I agree as well. I tested out the original poster's patch and it works great. Any way this can be made into a "PRAGMA strict_mode" so that it would be usage-specific rather than compile-specific? I asked about this on stackoverfolw as well:http://stackoverflow.com/questions/13383763/is-there-a-way-disable-lax-quoting-rules-in-sqlite/
--- On Thu, 11/15/12, John Gabriele <jmg3...@gmail.com> wrote: From: John Gabriele <jmg3...@gmail.com> Subject: Re: [sqlite] Stricter parsing rules To: "General Discussion of SQLite Database" <sqlite-users@sqlite.org> Date: Thursday, November 15, 2012, 1:56 PM On Wed, Nov 14, 2012 at 5:22 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 14 Nov 2012, at 9:46pm, BareFeetWare <list....@barefeetware.com> wrote: > >> 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. > > Me three. Perhaps this and a couple of similar things will be fixed in > SQLite4. Me four. The OP's practice of always using double-quotes for identifiers seems like a sound one, and it would be useful if sqlite could tell me if the thing I *think* is an identifier is actually not. ---John _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
