Entering SQL Statements - Mastering phpMyAdmin 3.4 for Effective MySQL Management - page 207

Let us send the same list of queries again and watch the results:
It is normal to receive a Duplicate entry error message that says the value
100 exists already. We are seeing the results of the first INSERT statement;
but what happens to the next one? Execution stops at the first error because
$cfg['IgnoreMultiSubmitErrors'] is set to FALSE telling phpMyAdmin not to
ignore errors in multiple statements. If it is set to TRUE , the program successively
tries all the statements, and we see two Duplicate entry errors.
This feature would not work as expected, if we tried more than one SELECT
statement. We would see the results of only the last SELECT statement.
Pretty printing (syntax highlighting)
By default, phpMyAdmin parses and highlights the various elements of any MySQL
statement it processes. This is controlled by $cfg['SQP']['fmtType'] , which is set
to 'html' by default. This mode uses a specific color for each different element (a
reserved word, a variable, a comment, and so on) as described in the $cfg['SQP']
['fmtColor'] array located in the theme-specific layout.inc.php file.
Setting fmtType to 'text' would remove all color formatting, inserting line breaks
at logical points inside a MySQL statement. Finally, setting fmtType to 'none'
removes every kind of formatting, leaving our syntax intact.
The SQL Validator
Each time phpMyAdmin transmits a query, the MySQL server interprets it and
provides feedback. The syntax of the query must follow MySQL rules, which are not
the same as the SQL Standard. However, conforming to SQL Standard ensures that
our queries are usable on other SQL implementations.