MySQL Manual
A Problems and Common Errors
- A.2 Common Errors When Using MySQL
- A.2.1
Access deniedError - A.2.2
MySQL server has gone awayError - A.2.3
Can't connect to [local] MySQL serverError - A.2.4
Client does not support authentication protocolerror - A.2.5
Host '...' is blockedError - A.2.6
Too many connectionsError - A.2.7
Some non-transactional changed tables couldn't be rolled backError - A.2.8
Out of memoryError - A.2.9
Packet too largeError - A.2.10 Communication Errors / Aborted Connection
- A.2.11
The table is fullError - A.2.12
Can't create/write to fileError - A.2.13
Commands out of syncError in Client - A.2.14
Ignoring userError - A.2.15
Table 'xxx' doesn't existError - A.2.16
Can't initialize character set xxxerror - A.2.17 File Not Found
- A.2.1
A.2.7 Some non-transactional changed tables couldn't be rolled back Error
If you get the error/warning: Warning: Some non-transactional
changed tables couldn't be rolled back when trying to do a
ROLLBACK, this means that some of the tables you used in the
transaction didn't support transactions. These non-transactional tables
will not be affected by the ROLLBACK statement.
The most typical case when this happens is when you have tried to create
a table of a type that is not supported by your mysqld binary.
If mysqld doesn't support a table type (or if the table type is
disabled by a startup option) , it will instead create the table type
with the table type that is most resembles to the one you requested,
probably MyISAM.
You can check the table type for a table by doing:
SHOW TABLE STATUS LIKE 'table_name'. See section 4.5.7.2 SHOW TABLE STATUS.
You can check the extensions your mysqld binary supports by doing:
show variables like 'have_%'. See section 4.5.7.4 SHOW VARIABLES.
