-----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 strings that way :-) Strings can and should be stored as strings. You would need to register a user defined function with SQLite that takes the hex encoding and returns a string. There is no other solution I can think of as you ruled out a 'host' language. It is possible to make dynamically loaded extensions that can provide the function although it will also require SQLite to have been called to enable them which is unlikely. If your final output can be html then you could output the field as is, and have some Javascript that finds them and converts to text. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk+PNowACgkQmOOfHg372QSCwgCgp9jYnBJ09zhrNNg6DYy9pBbI kuEAoKl0VFB5eghuYe6+14Xx6dO0cigE =4WcZ -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
