mirror of
https://github.com/django/django.git
synced 2025-08-04 19:08:28 +00:00
Documented that case-insensitive matching is not supported for non-ASCII
strings in SQLite. Refs #9905. git-svn-id: http://code.djangoproject.com/svn/django/trunk@9705 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
0c08368116
commit
3b489b7742
2 changed files with 47 additions and 2 deletions
|
@ -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
|
||||
------------------------
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue