I have these lines at the top of a MySQL .sql file (dumped with phpMyAdmin):
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */;
But they all seem to be commented out. So will MySQL ignore them when the file is loaded back into a database? If so, why generate these lines at all?
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).
INTO DUMPFILE is a SELECT clause which writes the resultset into a single unformatted row, without any separators, in a file. The results will not be returned to the client. file_path can be an absolute path, or a relative path starting from the data directory.
It is at either at root or in current directory where you run the dump command. try this command on terminal.. hmm.. locate myBackup.
These are conditional comments aimed at certain versions of mySQL.
From here and here:
/*!
*/
MySQL will parse and execute these lines of code, I believe for localization and character-encoding stuff, because the comments start with /*!
(with the exclamation mark) instead of just the C-style /*
.
Think of it the same way you do conditional comments and Internet Explorer. <!--[if IE]><![endif]-->
looks like any plain old HTML comment to other browsers, but IE recognizes this special comment and parses it as needed. Likewise, /*! */
looks like any other comment to other SQL DBMSes but is special to MySQL.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With