diff --git a/Docs/manual.texi b/Docs/manual.texi index 505fd171c70db5dfd2535366c3f389039ce4d3ae..6e2f274022e0846efb5b18bc2b5dae4b68c37c41 100644 --- a/Docs/manual.texi +++ b/Docs/manual.texi @@ -2982,9 +2982,11 @@ TABLE ... SELECT}. @cindex updating, tables @cindex @code{InnoDB} tables @cindex @code{BDB} tables +@cindex @code{ACID} MySQL supports transactions with the @code{InnoDB} and @code{BDB} @code{Transactional table handlers}. @xref{Table types}. +@code{InnoDB} provides @code{ACID} compliancy. However, the non-transactional table types in MySQL such as @code{MyISAM} follow another paradigm for data integrity called @@ -35611,9 +35613,13 @@ SUM_OVER_ALL_KEYS(max_length_of_key + sizeof(char*) * 2) @node InnoDB overview, InnoDB start, InnoDB, InnoDB @subsection InnoDB Tables Overview -InnoDB provides MySQL with a transaction-safe table handler with -commit, rollback, and crash recovery capabilities. InnoDB does -locking on row level and also provides an Oracle-style +@cindex transactions, support +@cindex transaction-safe tables +@cindex ACID + +InnoDB provides MySQL with a transaction-safe (@code{ACID} compliant) +table handler with commit, rollback, and crash recovery capabilities. +InnoDB does locking on row level and also provides an Oracle-style consistent non-locking read in @code{SELECT}s. These features increase multiuser concurrency and performance. There is no need for