The person I was working with pointed me to a little
used link on their
site, and I believe that all of us here should take a look at it when we
have time.
It's a link to get the draft copy of the SQL-200x standard, which,
according to him as he is on the ISO SQL committee, is fairly near ready
to be released. He also says there will be no more fixes to it, other than
spelling/typo fixes.
Here is the link:
http://www.jtc1sc32.org/sc32/jtc1sc32.nsf/23933607697154bf852566160054bcf7/…
You want the first PDF file.
Most notably in it, I find that some things that MySQL thinks are valid,
are NOT part of the SQL standard. ESP how it does the valid identifier
tokens that I had trouble with.
MySQL claims valid tokens are:
([A-Za-z$_0-9]*[a-zA-Z$_][A-Za-z$_0-9]*)
But the standard says:
([a-zA-Z][a-zA-Z_0-9]*)
There are a number of other things, so such a point where I have this
question:
Should we explictly support MySQL where it diverges from the standard, or
only support the SQL standard, with minimal MySQL extensions?
Yes, I think we should explicitely support MySQL, as phpMyAdmin is
strictly MySQL-oriented,
and we can expect our users to use whatever syntax MySQL offers.
Of course we can only hope that MySQL converges towards the official
standard.
Marc