Django

Code

Changeset 3436

Show
Ignore:
Timestamp:
07/23/06 21:39:50 (2 years ago)
Author:
adrian
Message:

Added 'Transactions in MySQL' section to docs/transactions.txt

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • django/trunk/docs/transactions.txt

    r2980 r3436  
    33============================== 
    44 
    5 Django gives you a few ways to control how database transactions are managed. 
     5Django gives you a few ways to control how database transactions are managed, 
     6if you're using a database that supports transactions. 
    67 
    78Django's default transaction behavior 
    …… 
    145146all situations, you'll be better off using the default behavior, or the 
    146147transaction middleware, and only modify selected functions as needed. 
     148 
     149Transactions in MySQL 
     150===================== 
     151 
     152If you're using MySQL, your tables may or may not support transactions; it 
     153depends on your MySQL version and the table types you're using. (By 
     154"table types," we mean something like "InnoDB" or "MyISAM".) MySQL transaction 
     155peculiarities are outside the scope of this article, but the MySQL site has 
     156`information on MySQL transactions`_. 
     157 
     158If your MySQL setup does *not* support transactions, then Django will function 
     159in auto-commit mode: Statements will be executed and committed as soon as 
     160they're called. If your MySQL setup *does* support transactions, Django will 
     161handle transactions as explained in this document. 
     162 
     163.. _information on MySQL transactions: http://dev.mysql.com/books/mysqlpress/mysql-tutorial/ch10.html