summaryrefslogtreecommitdiffstats
path: root/user_guide/database/transactions.html
diff options
context:
space:
mode:
authoradmin <devnull@localhost>2006-10-11 01:38:05 +0200
committeradmin <devnull@localhost>2006-10-11 01:38:05 +0200
commita33ec0a3efc6e1c623966a210a83a67e1e253b9f (patch)
treed6f6f0deca95db5ce074538f7a7f0cfd4ba7209c /user_guide/database/transactions.html
parent1b0ab4665720446eee6b03f864bb5576e6065a4a (diff)
Diffstat (limited to 'user_guide/database/transactions.html')
-rw-r--r--user_guide/database/transactions.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/user_guide/database/transactions.html b/user_guide/database/transactions.html
index cf095ea85..8077155ed 100644
--- a/user_guide/database/transactions.html
+++ b/user_guide/database/transactions.html
@@ -67,11 +67,11 @@ Transactions
<h1>Transactions</h1>
<p>Code Igniter's database abstraction allows you to use <dfn>transactions</dfn> with databases that support transaction-safe table types. In MySQL, you'll need
-to be running InnoDB or BDB table types rather then the more common MyISAM. Most other databases support transactions natively.</p>
+to be running InnoDB or BDB table types rather then the more common MyISAM. Most other database platforms support transactions natively.</p>
<p>If you are not familiar with
transactions we recommend you find a good online resource to learn about them for your particular database. The information below assumes you
-have a basic understanding of transactions. For most sites, however, transactions won't be necessary.
+have a basic understanding of transactions.
</p>
<h2>Code Igniter's Approach to Transactions</h2>