Tutorial by Examples

select LastName, FirstName, from Person Returns message: Error Code: 1064. You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'from Person' at line 2. Getting a "1064 error" message from MySQL mean...

This error appears while trying to update or delete records without including the WHERE clause that uses the KEY column. To execute the delete or update anyway - type: SET SQL_SAFE_UPDATES = 0; To enable the safe mode again - type: SET SQL_SAFE_UPDATES = 1;

This error occurs when tables are not adequately structured to handle the speedy lookup verification of Foreign Key (FK) requirements that the developer is mandating. CREATE TABLE `gtType` ( `type` char(2) NOT NULL, `description` varchar(1000) NOT NULL, PRIMARY KEY (`type`) ) ENGINE=InnoD...

See discussions in "GRANT" and "Recovering root password".

Usually this means that the Master crashed and that sync_binlog was OFF. The solution is to CHANGE MASTER to POS=0 of the next binlog file (see the Master) on the Slave. The cause: The Master sends replication items to the Slave before flushing to its binlog (when sync_binlog=OFF). If the Master cr...

Check for a Firewall issue blocking port 3306. Some possible diagnostics and/or solutions Is the server actually running? "service firewalld stop" and "systemctl disable firewalld" telnet master 3306 Check the bind-address check skip-name-resolve check the socket.

1067 This is probably related to TIMESTAMP defaults, which have changed over time. See TIMESTAMP defaults in the Dates & Times page. (which does not exist yet) 1292/1366 DOUBLE/Integer Check for letters or other syntax errors. Check that the columns align; perhaps you think you are putting i...

When you try access the records from MySQL database, you may get these error messages. These error messages occurred due to corruption in MySQL database. Following are the types MySQL error code 126 = Index file is crashed MySQL error code 127 = Record-file is crashed MySQL error code 134 = Recor...

Error 139 may mean that the number and size of the fields in the table definition exceeds some limit. Workarounds: Re-think the schema Normalize some fields Vertically partition the table

This usually means that the character set handling was not consistent between client and server. See ... for further assistance.

(taking a break) With the inclusion of those 4 error numbers, I think this page will have covered about 50% of the typical errors users get. (Yes, this 'Example' needs revision.) 24 Can't open file (Too many open files) open_files_limit comes from an OS setting. table_open_cache needs to be les...