Ticket #6842: r8643.diff

docs/exceptions.txt

@@ +1 @@
+=================
+Django Exceptions
+=================
+
+This document describes the exceptions raised by Django.
+
+Django raises some Django specific exceptions as well as many standard Python exceptions.
+
+Django Specific Exceptions
+==========================
+
+Most of the Django specific exceptions are in the ``django.core.exceptions`` module.  For example, 
+``django.core.exceptions.ViewDoesNotExist``.
+
+ObjectDoesNotExist and DoesNotExist
+-----------------------------------
+The ``DoesNotExist`` exception is raised when an object is not found for the given parameters of a 
+query.  The ``DoesNotExist`` exception is not in ``django.core.exceptions``.  Instead, it is an 
+attribute of the model class and inherits from ``ObjectDoesNotExist`` which is in 
+``django.core.exceptions``.  See `get`_ for further information on ``ObjectDoesNotExist`` and 
+``DoesNotExist``.
+
+.. _`get`: ../db-api/#get-kwargs
+
+MultipleObjectsReturned
+-----------------------
+The ``MultipleObjectsReturned`` exception is raised by a query if only one object is expected, but 
+multiple objects are returned.  See `get`_ for further information.  The ``MultipleObjectsReturned`` 
+exception is an attribute of a model class and it is in ``django.core.exceptions``.
+
+.. _`get`: ../db-api/#get-kwargs
+
+SuspiciousOperation
+-------------------
+The ``SuspiciousOperation`` exception is raised when a user did something suspicious.
+
+PermissionDenied
+----------------
+The ``PermissionDenied`` exception is raised when a user does not have permission to perform the action 
+attempted.
+
+ViewDoesNotExist
+----------------
+The ``ViewDoesNotExist`` exception is raised by ``django.core.urlresolvers`` when a requested view does 
+not exist.
+
+MiddlewareNotUsed
+-----------------
+The ``MiddlewareNotUsed`` exception is raised when a middleware is not used in the server configuration.
+
+ImproperlyConfigured
+--------------------
+The ``ImproperlyConfigured`` exception is raised when Django is somehow improperly configured. 
+
+FieldError
+----------
+The ``FieldError`` exception is raised when there is a problem with a model field.  This can happen for 
+several reasons, some of which are:
+    
+    - A field in a model clashes with a field of the same name from an abstract base class
+    - An infinite loop is caused by ordering
+    - A keyword cannot be parsed from the filter parameters
+    - If a field cannot be determined from a keyword in the query parameters
+    - If a join is not permitted on the specified field
+    - If a field name is invalid
+    - If a query contains invalid order_by arguments
+
+Database Exceptions
+===================
+Django raises or propagates standard database exceptions, such as DatabaseError and IntegrityError, 
+when appropriate for operations on model objects.  See 
+`PEP 249 - Python Database API Specification v2.0`_ for further information about database exceptions.
+
+.. _`PEP 249 - Python Database API Specification v2.0`: http://www.python.org/dev/peps/pep-0249/
+
+Python Exceptions
+=================
+Django raises built-in Python exceptions when appropriate as well. See the Python `documentation`_ for 
+further information on the built-in exceptions. 
+
+.. _`documentation`: http://docs.python.org/lib/module-exceptions.html
+