Hi Ben,
I hit this a few months ago. Hex literals have to contain an even
number of hex digits. For that discussion, see:
http://www.nabble.com/Hexadecimal-Inequalities-Failing--td20216982.html
Thank you,
Clay
On Wed, 1 Jul 2009, Ben Atkinson wrote:
>
> Sorry for the newbie SQL question. I'm trying to use the INSERT INTO
> statement with a hexadecimal literal. I want to accomplish something
> like this:
>
> INSERT INTO TruckDefaultsTable VALUES ( 'AirPressureTime', 0, 0xB40000);
>
> sqlite chokes on the 0xB40000 expression with:
> unrecognized token: "0xB40000"
>
> I could express the value in decimal as 11796480, but that's pretty awkward
> since the actual value I'm putting into the table is a Linux timeval
> structure.
> It just makes more sense as hex.
>
> Does SQL have a hex literal sequence that serves the same role as "0x" in C?
>
> Thanks for any help.
>
> Ben
>
>
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
