From 87fc7efda5c0aaacca5a5f1a2e7e46e2b5489029 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Tue, 2 Dec 2008 05:58:15 +0000 Subject: [PATCH] Added a note to the SQLite database documentation mentioning that 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. git-svn-id: http://code.djangoproject.com/svn/django/trunk@9540 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/databases.txt | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 59ebff35c8..79e6136104 100644 --- a/docs/ref/databases.txt +++ b/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