At the moment phpMyAdmin extensively supports mysql.
When a user exports their database through phpmyadmin,
the exported file (locahost.sql) ends in a .sql
extension. Furthermore, the mysql engine proceses
imported and exported files and files are generated to
comply with addtional mysql sql grammer rules (beyond
the original sql grammer specs).
The localhost.sql file be renamed to localhost.mysql,
or localhost.mysql.sql (to imply that it confirms to
sql, but needs to maintain mysql syntax rules which at
the same time do conflict with sql conventions... see
If you are editing the sql file in a text editor, you
must comply with mysql grammer specs if you want the
file to be compatable with other phpmyadmin mysql
To anyone reviewing the file localhost.sql in their
favourite text editor (vim, emacs, whatever), it would
more benefiticial to have mysql syntax highlighting
apply to the file rather than sql syntax highlighting.
Mysql language syntax deviates in at least one area
from SQL syntax:
I found this (edited for conciseness) on mysql's
website (note the part about 'must be followed by a
space'... if you don't do that, the file won't import
successfuly back into mysql):
Standard SQL uses '--' as a start-comment sequence.
MySQL Server 3.23.3 and up also supports a variant of
the '--' comment style. That is, the '--' start-comment
sequence must be followed by a space (or by a control
character such as a newline).
The space is required to prevent problems with
automatically generated SQL queries that use constructs
Thoughts? This isn't a bug, per-se, but it prevents
bugs and can encourage more appropriate syntax
highlighting. I was importing back into phpmyadmin a
file I exported earlier, and made the mistake above
with comments. There, I learned that in this case,
mysql requires an update of sql specs.