The behaviour of quoting with [identifier] or `identifier` seems to do what you want, but, as the docs say, these are not standard SQL.
http://www.sqlite.org/lang_keywords.html It's not a great option, since it forces you to have nonstandard SQL, but it's a potentially useful one to have on the table. Dave. sqlite> create table jam (valid int); sqlite> insert into jam values (12); sqlite> select [invalid] from [jam]; Error: no such column: invalid sqlite> select `invalid` from jam; Error: no such column: invalid sqlite> select invalid from jam; Error: no such column: invalid sqlite> select "invalid" from jam; invalid sqlite> select 'invalid' from jam; invalid On Wed, Nov 14, 2012 at 10: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. > > Simon. > _______________________________________________ > 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
