Pavel Ivanov wrote: > It works because SQLite knows that people often mix single quotes and > double quotes. So when it sees something in double quotes it first > tries to match some identifier to that and if it fails then SQLite > considers it as a string constant. > > Pavel > > On Wed, Feb 3, 2010 at 5:20 PM, Ron Hudson <hudson...@gmail.com> wrote: > >> Pavel Ivanov wrote: >> >>> String constants should be enclosed in single quotes. Double quotes >>> are for identifiers. So in your case you make perfectly legal no-op >>> action - update field R with value of field R, i.e. leave field R >>> unchanged. >>> >>> Pavel >>> >>> >> Thanks Pavel, that works.. >> >> Hmm I wonder why "insert into checks >> values(null,"","value","value",1234.56....);" works... no matter. >> >> Ron. >> >> >> _______________________________________________ >> 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 > Oh, I understand - in fact I tried an insert with no quotes and sqlite marked an error where one of my data values was the same as one of my field names. It works fine if I use single quotes.
Thanks. Ron. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
