[1.0.X] 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.

Backport of r9540 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9542 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2008-12-02 06:01:14 +00:00
parent 931d96e065
commit c61ebbe2ba
1 changed files with 14 additions and 0 deletions

View File

@ -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