Eugene Wee wrote: >> >> If it does not have any compatibility with any other database, >> ONLY then I say that one should drop #3 quoting convention. >> > I believe that MySQL allows double quotes to be used as string > delimiters by default, but then this would not be a compatibility break > with MySQL since MySQL also supports the standard use of single quotes > for this purpose by default, and does not have the same "identifier, > else a string" behaviour anyway. >
It was added for MySQL compatibility. They support both single and double quotes as literal string delimiters. MySQL used nonstandard backquotes to delimit identifiers. MySQL has since added a ANSI_QUOTES mode which changes this behavior. From their documentation: "If the ANSI_QUOTES SQL mode is enabled, string literals can be quoted only within single quotes because a string quoted within double quotes is interpreted as an identifier." I also vote to have this (mis)-feature dropped (in fact I'm pretty sure I have suggested this several times in the past). If it can't be dropped outright, then at least add a pragma to disable the extensions and accept only standard quoting. The current behavior encourages users to use non-standard quoting to get useful error messages (see http://article.gmane.org/gmane.comp.db.sqlite.general/35531 for an example). Dennis Cote _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
