AFAIK, SQLite comes from the grass roots of PostgreSQL. Whatever 'standards' it adheres to, SQLite goes by. As a fact, I don't know what those standards are, and I don't care what they are. The documentation on SQLite.org says "This is how you use it", so that's how I'll use it.
Besides, SQL-xx, although called 'standards' are pretty much guidelines. Between the 4 major DB engines (MSSQL, PGSQL, MYSQL, and SQLite) all of them have their own tweaks and twists and methods of doing stuff. I've never used PGSQL beyond maybe two queries, but, getting a dump from one engine to another always requires some sort of hacking, or, change of code, or whatever you want to call it, to get the dump to work successfully. Mostly it is with initialization functions, but even with table creation and structures, I've found 'issues' I have to tackle on occasion. On Mon, Mar 21, 2016 at 6:32 AM, Dominique Devienne <ddevienne at gmail.com> wrote: > On Mon, Mar 21, 2016 at 11:01 AM, Cezary H. Noweta <chn at poczta.onet.pl> > wrote: > > > On 2016-03-21 08:57, Dominique Devienne wrote: > > > >> Seems like using square-brackets instead of double-quotes is > non-standard: > >> > >> > https://en.wikibooks.org/wiki/SQL_Dialects_Reference/Data_structure_definition/Delimited_identifiers > >> > > > > Explicitly documented by SQLite: > > > > And? That's still non-SQL standard. > > SQLite tries to be compatible with non-standard extensions > from various popular RDBMS', but when a standard alternative > exists, it should be preferred IMHO. --DD > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
