Thanks, Simon - it's a bug then. Hope it will get pulled into the bug tracker.
Igor Simon Slavin-3 wrote: > > > On 2 Aug 2011, at 1:10am, Igor Sereda wrote: > >> To my humble knowledge, operations with NULL have well-defined semantics, >> both in SQL-you-name-it standards and in SQLite. "A < B" may have three >> results - TRUE, FALSE and NULL. It doesn't matter whether you can make >> any >> sense of it - it's the spec ;) > > The spec for '<=' should say that comparing any number with NULL always > gives a NULL result. If SQLite is doing anything apart from that, it's a > bug. > > Okay, here it is: SQL92 8.2 (1) (a): > > "If XV or YV is the null value, then "X <comp op> Y" is unknown." > > In this context, returning 'unknown' means returning NULL. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > -- View this message in context: http://old.nabble.com/Virtual-Table-xBestIndex-and-NULL-Search-Conditions-%28Bug-%29-tp32172549p32175828.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
