MySQL Server supports three comment styles:
From a “
#” character to the end of the line.From a “
--” sequence to the end of the line. In MySQL, the “--” (double-dash) comment style requires the second dash to be followed by at least one whitespace or control character (such as a space, tab, newline, and so on). This syntax differs slightly from standard SQL comment syntax, as discussed in Section 1.9.5.7, “'--' as the Start of a Comment”.From a
/*sequence to the following*/sequence, as in the C programming language. This syntax allows a comment to extend over multiple lines because the beginning and closing sequences need not be on the same line.
The following example demonstrates all three comment styles:
mysql>SELECT 1+1; # This comment continues to the end of linemysql>SELECT 1+1; -- This comment continues to the end of linemysql>SELECT 1 /* this is an in-line comment */ + 1;mysql>SELECT 1+/*this is amultiple-line comment*/1;
MySQL Server supports some variants of C-style comments. These enable you to write code that includes MySQL extensions, but is still portable, by using comments of the following form:
/*! MySQL-specific code */
In this case, MySQL Server parses and executes the code within the
comment as it would any other SQL statement, but other SQL servers
will ignore the extensions. For example, MySQL Server recognizes
the STRAIGHT_JOIN keyword in the following
statement, but other servers will not:
SELECT /*! STRAIGHT_JOIN */ col1 FROM table1,table2 WHERE ...
If you add a version number after the
“!” character, the syntax within
the comment is executed only if the MySQL version is greater than
or equal to the specified version number. The
TEMPORARY keyword in the following comment is
executed only by servers from MySQL 3.23.02 or higher:
CREATE /*!32302 TEMPORARY */ TABLE t (a INT);
The comment syntax just described applies to how the mysqld server parses SQL statements. The mysql client program also performs some parsing of statements before sending them to the server. (It does this to determine statement boundaries within a multiple-statement input line.)
User Comments
Some tiny gotchas-- nothing serious. Using two dashes ('--') inside a regular comment block (/* ... */) __MAY__ confuse the parser and in which case you will get strange errors. Also using single apostrophe's (') can wig it out too. Not sure why this happens.
/*
this is a good comment
*/
/* this is a bad comment-- it has two dashes
and __MIGHT__ wig out the parser
(for some reason it doesn't always happen, haven't
figure out the how/when part yet)
*/
My guess is the Parser "Wigs Out" when you include the double dash on the same line as the */, so that it looks like this:
/* Start a Comment
-- Here's a nested comment */
Now, the parser saw the /* and the --, but because of the --, it didn't see the */ and so it thinks the original /* comment is still active. It closed the -- comment on the carriage return.
The parser should either NOT recognize nested comments, or be adjusted to allow for closing one comment while "technically" inside another.
note that mysql parser does not always interpret correctly C -style comments
1 row in set (0.00 sec)here's an example:
correct behaviour:
mysql> select 1+ /* aaa */ 2 jj;
"funny" :
mysql> select 1+ /* aaa */ 2;
1 row in set (0.00 sec)
and if you have new lines in the comment (just copy the example from the documentation) it gets too funny
One combination in a source'd file that just caused me grief is # embedded within /* */:
/* Insert #1 of 4 */
insert into foo (bar) values (1);
The insert is skipped (0 rows affected)
This is better:
/* Insert number 1 of 4 */
insert into foo (bar) values (1);
If your .sql files spontaneously stop working, make sure no text editors 'accidently' changed the newlines to MAC (CR), which would make # and -- comments run until the end of the file (MySQL won't output an error either).
Add your own comment.