[1.0.X] Documented that case-insensitive matching is not supported for non-ASCII

strings in SQLite. Refs #9905.

Backport of r9705 from trunk.

git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9706 bcc190cf-cafb-0310-a4f2-bffc1f526a37

1 files changed, 20 insertions, 0 deletions

diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt
index 0b5a819898..e553651ef3 100644
--- a/docs/ref/databases.txt
+++ b/docs/ref/databases.txt
@@ -265,6 +265,26 @@ of whether ``unique=True`` is specified or not.
 SQLite notes 
 ============ 
  
+SQLite_ provides an excellent development alternative for applications that
+are predominantly read-only or require a smaller installation footprint. As
+with all database servers, though, there are some differences that are
+specific to SQLite that you should be aware of.
+
+.. _SQLite: http://www.sqlite.org/
+
+.. _sqlite-string-matching:
+
+String matching for non-ASCII strings
+--------------------------------------
+
+SQLite doesn't support case-insensitive matching for non-ASCII strings. Some
+possible workarounds for this are `documented at sqlite.org`_, but they are
+not utilised by the default SQLite backend in Django. Therefore, if you are
+using the ``iexact`` lookup type in your queryset filters, be aware that it
+will not work as expected for non-ASCII strings.
+
+.. _documented at sqlite.org: http://www.sqlite.org/faq.html#q18
+
 Versions prior to 3.3.6
 ------------------------