On May 5, 2014, at 1:14 AM, James K. Lowden <jklow...@schemamania.org> wrote:
> To amplify the point, the issue isn't pure fussiness or obligation to > adhere to standards. A permissive parser invites error. Exactly. > It's not hard to imagine > > select 1 where 1 - 1; > > was intended as > > select 1 where 1 = 1; > > which, in the midst of a large query producing expected results, might > easily be overlooked. You must have been peering over my shoulder! This is exactly how this came about: a bloody typo! :D > I doubt Petite is confused by boolean evaluation, but rather is > dismayed by its appearance in this context. Indeed. I would have expected a syntax error along the lines of 'invalid relational operator’ or such. And that’s that. > > SQL is not C. To the extent the SQL supplied by SQLite is nonstandard, > it might as well be another language entirely. The better one knows > SQL, the harder a nonconformant implementation is to use. > > Not long ago I was helping someone with a query in MS Access. Easy, > just use a correlated subquery in an update statement. Hard, if > it chokes the parser. Perhaps you know the joke with the punchline, > "Assume a can opener." > > --jkl _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
