Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Added release notes for 4b31a6a.

Thanks Florian for reporting this omission.
  • Loading branch information...
commit ae417dd4d569669e8e1d8f15e643c6ba0820aafe 1 parent f5dbb56
Aymeric Augustin aaugustin authored
Showing with 26 additions and 1 deletion.
  1. +23 −0 docs/releases/1.6.txt
  2. +3 −1 docs/topics/db/transactions.txt
23 docs/releases/1.6.txt
View
@@ -66,6 +66,12 @@ UTC. This limitation was lifted in Django 1.6. Use :meth:`QuerySet.datetimes()
<django.db.models.query.QuerySet.datetimes>` to perform time zone aware
aggregation on a :class:`~django.db.models.DateTimeField`.
+Support for savepoints in SQLite
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Django 1.6 adds support for savepoints in SQLite, with some :ref:`limitations
+<savepoints-in-sqlite>`.
+
``BinaryField`` model field
~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -189,12 +195,29 @@ Backwards incompatible changes in 1.6
New transaction management model
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Behavior changes
+^^^^^^^^^^^^^^^^
+
Database-level autocommit is enabled by default in Django 1.6. While this
doesn't change the general spirit of Django's transaction management, there
are a few known backwards-incompatibities, described in the :ref:`transaction
management docs <transactions-upgrading-from-1.5>`. You should review your
code to determine if you're affected.
+Savepoints and ``assertNumQueries``
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The changes in transaction management may result in additional statements to
+create, release or rollback savepoints. This is more likely to happen with
+SQLite, since it didn't support savepoints until this release.
+
+If tests using :meth:`~django.test.TestCase.assertNumQueries` fail because of
+a higher number of queries than expected, check that the extra queries are
+related to savepoints, and adjust the expected number of queries accordingly.
+
+Autocommit option for PostgreSQL
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
In previous versions, database-level autocommit was only an option for
PostgreSQL, and it was disabled by default. This option is now :ref:`ignored
<postgresql-autocommit-mode>` and can be removed.
4 docs/topics/db/transactions.txt
View
@@ -372,11 +372,13 @@ The following example demonstrates the use of savepoints::
Database-specific notes
=======================
+.. _savepoints-in-sqlite:
+
Savepoints in SQLite
--------------------
While SQLite ≥ 3.6.8 supports savepoints, a flaw in the design of the
-:mod:`sqlite3` makes them hardly usable.
+:mod:`sqlite3` module makes them hardly usable.
When autocommit is enabled, savepoints don't make sense. When it's disabled,
:mod:`sqlite3` commits implicitly before savepoint statements. (In fact, it
Please sign in to comment.
Something went wrong with that request. Please try again.