On 9 Nov 2011, at 11:41am, Luuk wrote: > On 09-11-2011 11:15, Simon Slavin wrote: >> Is SQLite case-sensitive when parsing for NULL ? Does it identify things >> like 'nUlL' as NULL ? Can I rely on this behaviour in future versions ? > > Keywords should be case-insensitive, and NULL is a keyword....
Good. > But why this question? I mean why do you want to rely on it? > > It many cases it is much clearer to write every Keyword with capitals, > avoiding typo's I'll be doing an automated import inside a tiny hand-held device. A cut-down version of SQLite is very useful because the device itself needs to resort the data. But the device is extremely tiny and every byte I can save will be important. The data arrives as a comma-delimited list, like 31,7345,null,339 83,null,112,412 14,null,null,339 and I can turn this into INSERT commands very simply: INSERT INTO myTable VALUES( +dataline+ ) (I'm aware that Not having to parse and rearrange the incoming data makes my code extremely small and fast. Unfortunately, the detector which produces the data has gone through several firmware versions, and one expresses bad readings as 'Null' ! So I'm checking to see that I can get away without doing any preprocessing. Thanks for the answer. I have written code over the years which does things like IF A$ = "NULL" OR A$ = "null" THEN ... and wanted to make sure SQLite didn't have the same assumptions in. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
