summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorJohannes Dollinger <emulbreh@googlemail.com>2016-05-25 21:00:20 +0200
committerTim Graham <timograham@gmail.com>2016-08-08 10:43:34 -0400
commit46509cf13dbf049f75077981c29ef2c60b5a96ab (patch)
tree7e9400fede5c49a2cb2efa666d8fc44d0752ad3c /docs/ref
parentc002a0d39f18694f5e8a07d86684fc793b063056 (diff)
Moved EmpytResultSet to django.core.exceptions.
This removes the need for some inner imports.
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/exceptions.txt13
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/ref/exceptions.txt b/docs/ref/exceptions.txt
index c222010172..8c05aca977 100644
--- a/docs/ref/exceptions.txt
+++ b/docs/ref/exceptions.txt
@@ -24,6 +24,19 @@ Django core exception classes are defined in ``django.core.exceptions``.
See :meth:`~django.db.models.query.QuerySet.get()` for further information
on :exc:`ObjectDoesNotExist` and :exc:`~django.db.models.Model.DoesNotExist`.
+``EmptyResultSet``
+------------------
+
+.. exception:: EmptyResultSet
+
+ ``EmptyResultSet`` may be raised during query generation if a query won't
+ return any results. Most Django projects won't encounter this exception,
+ but it might be useful for implementing custom lookups and expressions.
+
+ .. versionchanged:: 1.11
+
+ In older versions, it's only importable from ``django.db.models.sql``.
+
``FieldDoesNotExist``
---------------------