I agree. this tolerance by SQLite for misquoted identifiers allows a lot of errors. I'd really like to see the rules tightened to remove ambiguous input.
Thanks, Tom Tom Brodhurst-Hill BareFeetWare -- iPhone/iPad/iPod and Mac software development, specialising in databases develo...@barefeetware.com -- Follow us on Twitter: http://twitter.com/barefeetware/ Like us on Facebook: http://www.facebook.com/BareFeetWare On 15/11/2012, at 7:37 AM, NSRT Mail account. <joecool2...@yahoo.com> wrote: > However, we've been bitten a few times by SQLite's compatibility features > which relax rules, and create ambiguity. > > When listing columns to retrieve in SELECT, or as part of a WHERE clause, we > always enclose our identifiers in double quotes. However, if a developer > accidentally misspells a column name, instead of failing with "Error: no such > column: xxxxxx", SQLite reinterprets the identifier as a string, and carries > on as if nothing happened. Sometimes such bugs go unnoticed for a while. > > Is there any way to make SQLite's parsing stricter? _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
