ansaurus

Question

Answer 1

+1 A:

Change the definition of the column to VARBINARY. The data you store in there doesn't seem to be an appropiate VARCHAR to start with.

This will ripple through the code that uses the column as you'll get a byte[] CLR tpe back in the client, and you should change your insert/update code accordingly. But after all, a passowrd hash is a byte[], not a string.

Remus Rusanu 2009-11-19 16:43:50

This sounds like a viable solution - I will look into it and let you know how it goes.

Keith 2009-11-19 17:15:21

I just tried this, however since we're tied to the third party algorithm, the system is obviously spitting out "can't convert byte[] to string" errors. And of course, this is in a proprietary DLL that we don't have access to modify the source. Do you have any suggestions for workarounds that don't involve modifying the core data types?

Keith 2009-11-19 17:25:48

You can always convert the byte[] to and from string, using Encoding.GetString() and Encoding.GetBytes(). http://msdn.microsoft.com/en-us/library/system.text.encoding.aspx. Another approach would be to Base64 encode the hash and store the base64, but sine it still needs to be converted to/from base64 for the sue of the library, I see no benefit over varbinary/byte[]

Remus Rusanu 2009-11-19 17:34:47

ansaurus

tags:

views:

answers:

Issues with Chr(0) in SQL INSERT script

related questions