From 510a16679d74b4a04df1b8552c6dc15ea2714463 Mon Sep 17 00:00:00 2001 From: Gary Wilson Jr Date: Tue, 31 Mar 2009 15:42:58 +0000 Subject: [PATCH] [1.0.X]: Fixed #10575 -- Fixed wording in database docs, patch from rduffield. Backport of r10252 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@10253 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/databases.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index d0ab9adae2..5fc14a34d7 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -311,10 +311,10 @@ version of ``pysqlite2`` (``pysqlite-2.x.x.win32-py2.5.exe``) that includes and uses a newer version of SQLite. Python 2.6 ships with a newer version of SQLite and is not affected by this issue. -If you are in such platform and find yourself in the need to update +If you are on such a platform and find yourself needing to update ``pysqlite``/SQLite, you will also need to manually modify the ``django/db/backends/sqlite3/base.py`` file in the Django source tree so it -attempts to import ``pysqlite2`` before than ``sqlite3`` and so it can take +attempts to import ``pysqlite2`` before ``sqlite3`` and so it can take advantage of the new ``pysqlite2``/SQLite versions. Version 3.6.2