diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt
index 4a52c5a..3c0ec4f 100644
|
a
|
b
|
managers, too.
|
| 161 | 161 | transactions. It tells Django you'll be managing the transaction on your |
| 162 | 162 | own. |
| 163 | 163 | |
| 164 | | If your view changes data and doesn't ``commit()`` or ``rollback()``, |
| 165 | | Django will raise a ``TransactionManagementError`` exception. |
| | 164 | Whether you are writing or simply reading from the database, you must |
| | 165 | ``commit()`` or ``rollback()`` explicitly or Django will raise a |
| | 166 | :exc:`TransactionManagementError` exception. This is required when reading |
| | 167 | from the database because ``SELECT`` statements may call functions which |
| | 168 | modify tables, and thus it is impossible to know if any data has been |
| | 169 | modified. |
| 166 | 170 | |
| 167 | 171 | Manual transaction management looks like this:: |
| 168 | 172 | |