On Wed, Apr 18, 2012 at 6:38 PM, Jim Sanders wrote:
>
> It's disappointing there isn't a simple "unhex()" function to do the
> reverse of the already existing function.
>
Code to implement such a function is contained in the SQLite test suite.
See it here:
http://www.sqlite.org/src/artifact/6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/04/12 15:38, Jim Sanders wrote:
> It's disappointing there isn't a simple "unhex()" function to do the
> reverse of the already existing function. That would be a very
> elegant solution to this issue, as I am so close.
unhex isn't anywhere n
Well yes I agree the stored format isn't ideal, but unfortunately I have no
control over that. These are hard drive serial numbers and that is the
format that Microsoft WMI spits them out in. It's possible that the
Spiceworks application could be modified to decode those hex strings it
gets bac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/04/12 14:39, Jim Sanders wrote:
> I found that, but I need essentially the reverse of that. The data
> stored in SQL is 3061626364 and I need to convert it back to 0abcd
> (from your example)
The correct fix is to get them to stop storing stri
I found that, but I need essentially the reverse of that. The data stored
in SQL is 3061626364 and I need to convert it back to 0abcd (from your
example)
On Wed, Apr 18, 2012 at 5:35 PM, Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 18/04/12 14:30, Jim Sanders wro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/04/12 14:30, Jim Sanders wrote:
> But I can't figure out a way do this dynamically for all rows.
There is a builtin hex() function.
sqlite> create table foo(bar); insert into foo values('0abcd');
sqlite> select hex(bar) from foo;
30616263
6 matches
Mail list logo
