Gavin Kistner wrote:
>> My point can perhaps better be described by example:
>> (written on my phone; please replace all • with backticks)
>> sqlite> create table perverse (•select• text, •••select••• text);
>> sqlite> insert into perverse values ('a','b');
>> sqlite> select •select•, •••select••• from perverse;
>> select|•select•
>> a|b
>>
>> In the above, "•select•" is very different from "select".
>>
Yes, you are correct, using identifier quoting you can embed quotes and
other special characters (like spaces) into an identifier name. I missed
your point.
create table t ("a `col ] with [ various quote""s `embedded`'");
>> (As an aside, here's a fun bug: try "select * from perverse" and see
>> if you can guess what will be shown in sqlite.)
>>
I get column names of
select|select
Yes, that would be another bug. The second columns name should include
the back ticks that were escaped by doubling them inside the outer back
tick quotes. SQLite seems to get confused because the quotes appear at
the ends of the identifier string.
Have you filed a bug report to see in any of these can be resolved?
Dennis Cote
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
