diff options
| author | Aymeric Augustin <aymeric.augustin@m4x.org> | 2014-01-26 09:30:10 +0100 |
|---|---|---|
| committer | Aymeric Augustin <aymeric.augustin@m4x.org> | 2014-01-26 09:30:10 +0100 |
| commit | 8e1fc0349124d4a792e02bfd4c90576f9e3bda95 (patch) | |
| tree | 6c9d6eeb7bb7e1a4a26dd93ae55ab02d19a27cdb | |
| parent | 9ffab9cee1a5bd1a2f6c326ae970d92526f9a304 (diff) | |
Fixed typo. Refs #21836.
| -rw-r--r-- | docs/topics/db/transactions.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt index 2bf545d12f..52a2a66780 100644 --- a/docs/topics/db/transactions.txt +++ b/docs/topics/db/transactions.txt @@ -240,7 +240,7 @@ back. This isn't always convenient for application developers. To alleviate this problem, most databases provide an autocommit mode. When autocommit is turned on and no transaction is active, each SQL query gets wrapped in its own -transaction. In other words, not only does each such query starts a +transaction. In other words, not only does each such query start a transaction, but the transaction also gets automatically committed or rolled back, depending on whether the query succeeded. |