1
0
mirror of https://github.com/django/django.git synced 2025-07-04 17:59:13 +00:00

[1.2.X] Updated an old workaround described in the Oracle backend notes with more modern advice.

Backport of r14637 from trunk.

git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.2.X@14638 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Ian Kelly 2010-11-20 01:15:14 +00:00
parent b199cb36f3
commit 84d809d822

View File

@ -650,9 +650,9 @@ some limitations on the usage of such LOB columns in general:
* LOB columns may not be used in a ``SELECT DISTINCT`` list. This means that * LOB columns may not be used in a ``SELECT DISTINCT`` list. This means that
attempting to use the ``QuerySet.distinct`` method on a model that attempting to use the ``QuerySet.distinct`` method on a model that
includes ``TextField`` columns will result in an error when run against includes ``TextField`` columns will result in an error when run against
Oracle. A workaround to this is to keep ``TextField`` columns out of any Oracle. As a workaround, use the ``QuerySet.defer`` method in conjunction
models that you foresee performing ``distinct()`` queries on, and to with ``distinct()`` to prevent ``TextField`` columns from being included in
include the ``TextField`` in a related model instead. the ``SELECT DISTINCT`` list.
.. _third-party-notes: .. _third-party-notes: