Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Added release notes for 4b31a6a.

Thanks Florian for reporting this omission.
  • Loading branch information...
commit ae417dd4d569669e8e1d8f15e643c6ba0820aafe 1 parent f5dbb56
Aymeric Augustin authored March 24, 2013
23  docs/releases/1.6.txt
@@ -66,6 +66,12 @@ UTC. This limitation was lifted in Django 1.6. Use :meth:`QuerySet.datetimes()
66 66
 <django.db.models.query.QuerySet.datetimes>` to perform time zone aware
67 67
 aggregation on a :class:`~django.db.models.DateTimeField`.
68 68
 
  69
+Support for savepoints in SQLite
  70
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  71
+
  72
+Django 1.6 adds support for savepoints in SQLite, with some :ref:`limitations
  73
+<savepoints-in-sqlite>`.
  74
+
69 75
 ``BinaryField`` model field
70 76
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
71 77
 
@@ -189,12 +195,29 @@ Backwards incompatible changes in 1.6
189 195
 New transaction management model
190 196
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
191 197
 
  198
+Behavior changes
  199
+^^^^^^^^^^^^^^^^
  200
+
192 201
 Database-level autocommit is enabled by default in Django 1.6. While this
193 202
 doesn't change the general spirit of Django's transaction management, there
194 203
 are a few known backwards-incompatibities, described in the :ref:`transaction
195 204
 management docs <transactions-upgrading-from-1.5>`. You should review your
196 205
 code to determine if you're affected.
197 206
 
  207
+Savepoints and ``assertNumQueries``
  208
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  209
+
  210
+The changes in transaction management may result in additional statements to
  211
+create, release or rollback savepoints. This is more likely to happen with
  212
+SQLite, since it didn't support savepoints until this release.
  213
+
  214
+If tests using :meth:`~django.test.TestCase.assertNumQueries` fail because of
  215
+a higher number of queries than expected, check that the extra queries are
  216
+related to savepoints, and adjust the expected number of queries accordingly.
  217
+
  218
+Autocommit option for PostgreSQL
  219
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  220
+
198 221
 In previous versions, database-level autocommit was only an option for
199 222
 PostgreSQL, and it was disabled by default. This option is now :ref:`ignored
200 223
 <postgresql-autocommit-mode>` and can be removed.
4  docs/topics/db/transactions.txt
@@ -372,11 +372,13 @@ The following example demonstrates the use of savepoints::
372 372
 Database-specific notes
373 373
 =======================
374 374
 
  375
+.. _savepoints-in-sqlite:
  376
+
375 377
 Savepoints in SQLite
376 378
 --------------------
377 379
 
378 380
 While SQLite ≥ 3.6.8 supports savepoints, a flaw in the design of the
379  
-:mod:`sqlite3` makes them hardly usable.
  381
+:mod:`sqlite3` module makes them hardly usable.
380 382
 
381 383
 When autocommit is enabled, savepoints don't make sense. When it's disabled,
382 384
 :mod:`sqlite3` commits implicitly before savepoint statements. (In fact, it

0 notes on commit ae417dd

Please sign in to comment.
Something went wrong with that request. Please try again.