D. Richard Hipp wrote: > 3. Double-quoted names fall back to being string literals if > there is no matching table or column name. > > So I'm giving some thought to removing feature (3) above and > disallowing double-quoted string literals. My concern is, though, > that this might break many existing applications. > > What opinion do you, gentle users, have of this matter?
I think you should go ahead and make the change you propose, and soon as possible. But release that change as version 3.7.0 so it is more clear to people that this is a significant change as far as the user experience goes, that they should realize this might break something if they were relying on the old broken behaviour, and that they need to fix their own code. I don't agree with having a pragma to turn on the old behavior, but I do like the idea of issuing warnings when it appears that a user may be relying on the old behavior; these warnings can help them track down what areas of their code need to be fixed. Or alternately make a 3.6.x series release first that adds warnings but keeps the old behaviour, then make a 3.7.0 release that keeps the warnings (modified if needed) but drops the bad behaviour. Note that any warnings like this should be possible to turn off when the user knows that their code is compliant and their string literals shouldn't be checked anymore for similarity to column names etc. -- Darren Duncan _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
