Browse files

[1.0.X] Added a note to the SQLite database documentation mentioning …


version 3.6.2 is to be avoided like the plague. Fortunately, it was only the
latest release for three weeks, so avoidance is easy (as is upgrading).

Refs #9358.

Backport of r9540 from trunk.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 931d96e commit c61ebbe2bac2f1b0a746465e84415564f03876c2 @malcolmt malcolmt committed Dec 2, 2008
Showing with 14 additions and 0 deletions.
  1. +14 −0 docs/ref/databases.txt
@@ -249,6 +249,9 @@ matter unless you're printing out the field values and are expecting to see
SQLite notes
+Versions prior to 3.3.6
Versions of SQLite 3.3.5 and older `contain a bug`_ when handling ``ORDER BY``
parameters. This can cause problems when you use the ``select`` parameter for
the ``extra()`` QuerySet method. The bug can be identified by the error message
@@ -278,6 +281,17 @@ If you are in such platform and find yourself in the need to update
attempts to import ``pysqlite2`` before than ``sqlite3`` and so it can take
advantage of the new ``pysqlite2``/SQLite versions.
+Version 3.6.2
+SQLite version 3.6.2 (released August 30, 2008) introduced a bug into ``SELECT
+DISTINCT`` handling that is triggered by, amongst other things, Django's
+``DateQuerySet`` (returned by the ``dates()`` method on a queryset).
+You should avoid using this version of SQLite with Django. Either upgrade to
+3.6.3 (released September 22, 2008) or later, or downgrade to an earlier
+version of SQLite.
.. _oracle-notes:
Oracle notes

0 comments on commit c61ebbe

Please sign in to comment.