> 3. Double-quoted names fall back to being string literals if > there is no matching table or column name. > > In retrospect, (3) seems to be a bad idea. It is accident-prone and > leads to all kinds of confusion. For example, if double-quotes are > being used correctly (which is to say to quote table or column names) > but a misspelling occurs in the name, the token reverts to being a > string literal rather than throwing an error. Or if a double-quoted > string really is being used as a string literal, but later a new > column is added to a table that has the same name as the string text, > the string literal will suddenly take on the value of the column...
> So I'm giving some thought to removing feature (3) above and > disallowing double-quoted string literals. Yes, absolutely, get rid of it, for exactly the reasons you mention above. It's currently a ridiculous situation where adding a column to a table can change the output of existing queries, and that a misspelled column name doesn't return an error. Thanks, Tom BareFeet _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
