Django は普通の Python の例外の他に、いくつか独自の例外も起こします。
\nDjango core 例外クラスは django.core.exceptions で定義されています。
AppRegistryNotReadyLink to this heading#This exception is raised when attempting to use models before the app\nloading process, which initializes the ORM, is\ncomplete.
\nObjectDoesNotExistLink to this heading#The base class for Model.DoesNotExist exceptions. A try/except for\nObjectDoesNotExist will catch\nDoesNotExist exceptions for all models.
See get().
EmptyResultSetLink to this heading#EmptyResultSet may be raised during query generation if a query won't\nreturn any results. Most Django projects won't encounter this exception,\nbut it might be useful for implementing custom lookups and expressions.
FieldDoesNotExistLink to this heading#The FieldDoesNotExist exception is raised by a model's\n_meta.get_field() method when the requested field does not exist on the\nmodel or on the model's parents.
MultipleObjectsReturnedLink to this heading#The base class for Model.MultipleObjectsReturned exceptions. A\ntry/except for MultipleObjectsReturned will catch\nMultipleObjectsReturned exceptions for all\nmodels.
See get().
SuspiciousOperationLink to this heading#The SuspiciousOperation exception is raised when a user has\nperformed an operation that should be considered suspicious from a security\nperspective, such as tampering with a session cookie. Subclasses of\nSuspiciousOperation include:
DisallowedHost
DisallowedModelAdminLookup
DisallowedModelAdminToField
DisallowedRedirect
InvalidSessionKey
RequestDataTooBig
SuspiciousFileOperation
SuspiciousMultipartForm
SuspiciousSession
TooManyFieldsSent
If a SuspiciousOperation exception reaches the ASGI/WSGI handler level\nit is logged at the Error level and results in\na HttpResponseBadRequest. See the logging\ndocumentation for more information.
PermissionDeniedLink to this heading#PermissionDenied 例外は、ユーザーにリクエストされたアクションを実行する権限がない場合に発生します。
ViewDoesNotExistLink to this heading#ViewDoesNotExist 例外は、リクエストされたビューが存在しないい場合に、django.urls によって発生します。
MiddlewareNotUsedLink to this heading#MiddlewareNotUsed 例外は、サーバーの設定の中でミドルウェアが使用されなかった時に発生します。
ImproperlyConfiguredLink to this heading#ImproperlyConfigured 例外は、Django が何らかの点で不適切に設定されている場合に発生します。たとえば、settings.py に含まれる値が不正であったり、パースできないような場合が考えられます。
FieldErrorLink to this heading#FieldError 例外は、モデルのフィールドに問題がある時に発生します。発生理由としては、次のようないくつかの理由が考えられます。
A field in a model clashes with a field of the same name from an\nabstract base class
An infinite loop is caused by ordering
A keyword cannot be parsed from the filter parameters
A field cannot be determined from a keyword in the query\nparameters
A join is not permitted on the specified field
A field name is invalid
A query contains invalid order_by arguments
ValidationErrorLink to this heading#ValidationError 例外は、データがフォームまたはモデルのフィールド検証に失敗すると発生します。検証 (validation) のより詳しい情報については、Form and Field Validation や Model Field Validation、Validator Reference を参照してください。
NON_FIELD_ERRORSLink to this heading#ValidationErrors that don't belong to a particular field in a form\nor model are classified as NON_FIELD_ERRORS. This constant is used\nas a key in dictionaries that otherwise map fields to their respective\nlist of errors.
RequestAbortedLink to this heading#The RequestAborted exception is raised when a HTTP body being read\nin by the handler is cut off midstream and the client connection closes,\nor when the client does not send data and hits a timeout where the server\ncloses the connection.
It is internal to the HTTP handler modules and you are unlikely to see\nit elsewhere. If you are modifying HTTP handling code, you should raise\nthis when you encounter an aborted request to make sure the socket is\nclosed cleanly.
\nSynchronousOnlyOperationLink to this heading#The SynchronousOnlyOperation exception is raised when code that\nis only allowed in synchronous Python code is called from an asynchronous\ncontext (a thread with a running asynchronous event loop). These parts of\nDjango are generally heavily reliant on thread-safety to function and don't\nwork correctly under coroutines sharing the same thread.
If you are trying to call code that is synchronous-only from an\nasynchronous thread, then create a synchronous thread and call it in that.\nYou can accomplish this is with asgiref.sync.sync_to_async().
URL Resolver の例外は django.urls で定義されています。
Resolver404Link to this heading#The Resolver404 exception is raised by\nresolve() if the path passed to resolve() doesn't\nmap to a view. It's a subclass of django.http.Http404.
NoReverseMatchLink to this heading#The NoReverseMatch exception is raised by django.urls when a\nmatching URL in your URLconf cannot be identified based on the parameters\nsupplied.
データベースの例外は django.db からインポートできます。
Django wraps the standard database exceptions so that your Django code has a\nguaranteed common implementation of these classes.
\nThe Django wrappers for database exceptions behave exactly the same as\nthe underlying database exceptions. See PEP 249, the Python Database API\nSpecification v2.0, for further information.
\nAs per PEP 3134, a __cause__ attribute is set with the original\n(underlying) database exception, allowing access to any additional\ninformation provided.
Raised to prevent deletion of referenced objects when using\ndjango.db.models.PROTECT. models.ProtectedError is a subclass\nof IntegrityError.
Raised to prevent deletion of referenced objects when using\ndjango.db.models.RESTRICT. models.RestrictedError is a subclass\nof IntegrityError.
Http の例外は django.http からインポートすることができます。
UnreadablePostErrorLink to this heading#UnreadablePostError は、ユーザーがアップロードをキャンセルすると発生します。
トランザクションの例外は django.db.transaction で定義されています。
TransactionManagementErrorLink to this heading#TransactionManagementError が発生するのは、データベースのトランザクションに関するあらゆる問題に対してです。
django.test パッケージが提供する例外です。
RedirectCycleErrorLink to this heading#RedirectCycleError は、テストクライアントがループまたは過度に長いリダイレクトチェーンを検出した時に発生します。
Django は、十分適切な場合にはビルトインの Python の例外を起こします。詳しい情報については、Python のドキュメント Built-in Exceptions を読んでください。
\n