On May 5, 2014, at 8:21 PM, RSmith <rsm...@rsweb.co.za> wrote: > the idea that introducing more complication will make erros/bugs less is just > false.
Straw man argument, unrelated to the topic at hand. This is solely about the SQL parser failing short of reporting syntax errors for nonsensical queries. select 1 where null; select 1 where is null; Error: near "is": syntax error select 1 where not null; select 1 where is not null; Error: near "is": syntax error select 1 where not( not null); elect 1 where not( is null ); Error: near "is": syntax error select 1 where not( 1 ); select 1 where ‘When I use a word, Humpty Dumpty said, in rather a scornful tone, it means just what I choose it to mean — neither more nor less.’; select 1 where not 'The question is, said Alice, whether you can make words mean so many different things.’; _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
