(mysql.info.gz) Non-transactional tables
Info Catalog
(mysql.info.gz) Problems with alias
(mysql.info.gz) Query Issues
(mysql.info.gz) Deleting from related tables
A.5.5 Rollback Failure for Non-Transactional Tables
---------------------------------------------------
If you receive the following message when trying to perform a
`ROLLBACK', it means that one or more of the tables you used in the
transaction do not support transactions:
Warning: Some non-transactional changed tables couldn't be rolled back
These non-transactional tables will not be affected by the `ROLLBACK'
statement.
If you were not deliberately mixing transactional and non-transactional
tables within the transaction, the most likely cause for this message is
that a table you thought was transactional actually is not. This can
happen if you try to create a table using a transactional storage
engine that is not supported by your `mysqld' server (or that was
disabled with a startup option). If `mysqld' doesn't support a storage
engine, it will instead create the table as a `MyISAM' table, which is
non-transactional.
You can check the table type for a table by using either of these
statements:
SHOW TABLE STATUS LIKE 'TBL_NAME';
SHOW CREATE TABLE TBL_NAME;
See `SHOW TABLE STATUS' SHOW TABLE STATUS. and `SHOW
CREATE TABLE' SHOW CREATE TABLE.
You can check which storage engines your `mysqld' server supports by
using this statement:
SHOW ENGINES;
Before MySQL 4.1.2, `SHOW ENGINES' is unavailable. Use the following
statement instead and check the value of the variable that is associated
with the storage engine in which you are interested:
SHOW VARIABLES LIKE 'have_%';
For example, to determine whether the `InnoDB' storage engine is
available, check the value of the `have_innodb' variable.
See `SHOW ENGINES' SHOW ENGINES. and `SHOW VARIABLES'
SHOW VARIABLES.
Info Catalog
(mysql.info.gz) Problems with alias
(mysql.info.gz) Query Issues
(mysql.info.gz) Deleting from related tables
automatically generated byinfo2html