Skip navigation links

Additional languages
MySQL 5.0 Reference Manual :: 1 General Information :: 1.8 MySQL Standards Compliance :: 1.8.5 MySQL Differences from Standard SQL
1.8.5.1 SELECT INTO TABLE »
Section Navigation      [Toggle]

1.8.5. MySQL Differences from Standard SQL

[+/-]

1.8.5.1. SELECT INTO TABLE
1.8.5.2. Transactions and Atomic Operations
1.8.5.3. Stored Routines and Triggers
1.8.5.4. Foreign Keys
1.8.5.5. Views
1.8.5.6. '--' as the Start of a Comment

We try to make MySQL Server follow the ANSI SQL standard and the ODBC SQL standard, but MySQL Server performs operations differently in some cases:

  • For VARCHAR columns, trailing spaces are removed when the value is stored. (This is fixed in MySQL 5.0.3). See Section B.1.8, “Known Issues in MySQL”.

  • In some cases, CHAR columns are silently converted to VARCHAR columns when you define a table or alter its structure. (This no longer occurs as of MySQL 5.0.3). See Section 12.1.5.1, “Silent Column Specification Changes”.

  • There are several differences between the MySQL and standard SQL privilege systems. For example, in MySQL, privileges for a table are not automatically revoked when you delete a table. You must explicitly issue a REVOKE statement to revoke privileges for a table. For more information, see Section 12.5.1.5, “REVOKE Syntax”.

  • The CAST() function does not support cast to REAL or BIGINT. See Section 11.9, “Cast Functions and Operators”.

  • Standard SQL requires that a HAVING clause in a SELECT statement be able to refer to columns in the GROUP BY clause. This cannot be done before MySQL 5.0.2.