diff options
author | unknown <jcole@main.burghcom.com> | 2001-05-01 04:12:23 -0400 |
---|---|---|
committer | unknown <jcole@main.burghcom.com> | 2001-05-01 04:12:23 -0400 |
commit | 449c819b444e71915931645d49ba855400f3e216 (patch) | |
tree | d1bc05f59743e6a03a3b28baade203b934984246 /Docs | |
parent | d067af6a168860548f31175966bfc830028dd5f6 (diff) | |
download | mariadb-git-449c819b444e71915931645d49ba855400f3e216.tar.gz |
manual.texi fixed paragraph
Docs/manual.texi:
fixed paragraph
BitKeeper/etc/logging_ok:
Logging to logging@openlogging.org accepted
Diffstat (limited to 'Docs')
-rw-r--r-- | Docs/manual.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Docs/manual.texi b/Docs/manual.texi index f42e6362d5d..704cd4b3414 100644 --- a/Docs/manual.texi +++ b/Docs/manual.texi @@ -22489,11 +22489,11 @@ non-transactional table will not change. If you are using @code{BEGIN} or @code{SET AUTOCOMMIT=0}, you should use the @strong{MySQL} binary log for backups instead of the -old update log; The transaction is stored in the binary log -in one chunk, during @code{COMMIT}, the to ensure and @code{ROLLBACK}:ed -transactions are not stored. @xref{Binary log}. +older update log. Transactions are stored in the binary log +in one chunk, upon @code{COMMIT}, to ensure that transactions which are +rolled back are not stored. @xref{Binary log}. -The following commands automatically ends an transaction (as if you had done +The following commands automatically end a transaction (as if you had done a @code{COMMIT} before executing the command): @multitable @columnfractions .33 .33 .33 |