On Tue, Sep 24, 2013 at 9:39 PM, Richard Hipp <d...@sqlite.org> wrote:
> On Tue, Sep 24, 2013 at 2:02 PM, Petite Abeille <petite.abei...@gmail.com > >wrote: > > On Sep 24, 2013, at 7:59 PM, Dan Kennedy <danielk1...@gmail.com> wrote: > > > A double quoted string is treated as a column name if possible, or a > > > string literal otherwise. It's an SQL thing. > > > > Nah. The second part is a SQLite thing. Randomly converting identifiers > > into literals is more of a misfeature. > > It was originally intended as a feature to provide enhanced MySQL > compatibility, since MySQL used to *require* double-quotes on strings. > Yes, it is something of a misfeature now, but we cannot change it without > breaking backwards compatibility. > Unless there's an opt-in pragma to enforce maximum conformance on this, the recently discussed statement-invariant 'now', etc... --DD _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
