From 46509cf13dbf049f75077981c29ef2c60b5a96ab Mon Sep 17 00:00:00 2001 From: Johannes Dollinger Date: Wed, 25 May 2016 21:00:20 +0200 Subject: Moved EmpytResultSet to django.core.exceptions. This removes the need for some inner imports. --- docs/ref/exceptions.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'docs') 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`` --------------------- -- cgit v1.3