Error Handling

• Error handling in InnoDB is not always the same as specified in the SQL standard.
  • According to the standard, any error during an SQL statement should cause the rollback of that statement.
  • InnoDB sometimes rolls back only part of the statement, or the whole transaction.

• The following items describe how InnoDB performs error handling:
  • If there is no more file space in the tablespace, a MySQL Table is full error occurs and InnoDB rolls back the SQL statement.
  • A transaction deadlock causes InnoDB to roll back the entire transaction.
    • In the case of a lock wait timeout, InnoDB rolls back only the most recent SQL statement.
  • When a transaction rollback occurs due to a deadlock or lock wait timeout, it cancels the effect of the statements within the transaction.
  • A duplicate-key error rolls back the SQL statement, if the IGNORE option was not specified in the statement.
  • A row too long error rolls back the SQL statement.

Are there any restrictions on InnoDB tables?

---

---

© 2007 John Michael Pierobon

Notes