diff options
| author | Ian Kelly <ian.g.kelly@gmail.com> | 2010-11-20 01:15:14 +0000 |
|---|---|---|
| committer | Ian Kelly <ian.g.kelly@gmail.com> | 2010-11-20 01:15:14 +0000 |
| commit | 84d809d8228cde8b4a1f7c566b3915678629c7b6 (patch) | |
| tree | d21e674767f321ed24e38d1359fd415627272568 /docs | |
| parent | b199cb36f3e236f468386c1c36a14a5eb20ebfaf (diff) | |
[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
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ref/databases.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index d89e01dfa8..0d93ab2567 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -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 attempting to use the ``QuerySet.distinct`` method on a model that includes ``TextField`` columns will result in an error when run against - Oracle. A workaround to this is to keep ``TextField`` columns out of any - models that you foresee performing ``distinct()`` queries on, and to - include the ``TextField`` in a related model instead. + Oracle. As a workaround, use the ``QuerySet.defer`` method in conjunction + with ``distinct()`` to prevent ``TextField`` columns from being included in + the ``SELECT DISTINCT`` list. .. _third-party-notes: |