mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-18 13:02:28 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Increased mentioning ACID compliancy of InnoDB.

Browse source
This commit is contained in:
arjen@co3064164-a.bitbike.com 2001-11-15 11:43:09 +10:00
parent 060a85faeb
commit 65bc25f8ca
1 changed files with 9 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
Docs/manual.texi
View file

@ -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