Closed GoogleCodeExporter closed 9 years ago
That's correct behaviour:
| CREATE statement uses single quotes for table name and fields
It uses what you used when you created the table. It doesn't touch the original
create table statement at all.
Moreover, using single quotes in this context is correct, because when you
create a table, the table name is a value, not a reference to an already
existing db-object (because the table does not exist yet).
| INSERT uses double quotes for table and fields
Which is correct. See https://www.sqlite.org/lang_keywords.html .
| single quotes for values.
Which is correct. See https://www.sqlite.org/lang_keywords.html .
Original comment by crazy4ch...@gmail.com
on 21 Mar 2013 at 1:15
Ok, sorry con the inconvenience.
I've noticed the problem because when using the generated SQL I've needed
change the double quotes to single quotes (instead of escape) to use inside a
string. When warned about this I've think that was a problem not is real
behavior..
Original comment by is2cool...@gmail.com
on 21 Mar 2013 at 3:54
Original issue reported on code.google.com by
is2cool...@gmail.com
on 21 Mar 2013 at 10:42