Django raises some of its own exceptions as well as standard Python exceptions.
Kelas-kelas pengecualian inti django ditentukan dalam django.core.exceptions
.
AppRegistryNotReady
¶AppRegistryNotReady
[sumber]¶This exception is raised when attempting to use models before the app loading process, which initializes the ORM, is complete.
ObjectDoesNotExist
¶ObjectDoesNotExist
[sumber]¶The base class for Model.DoesNotExist
exceptions. A try/except
for
ObjectDoesNotExist
will catch
DoesNotExist
exceptions for all models.
See get()
.
EmptyResultSet
¶FieldDoesNotExist
¶MultipleObjectsReturned
¶MultipleObjectsReturned
[sumber]¶The base class for Model.MultipleObjectsReturned
exceptions. A
try/except
for MultipleObjectsReturned
will catch
MultipleObjectsReturned
exceptions for all
models.
See get()
.
SuspiciousOperation
¶SuspiciousOperation
[sumber]¶The SuspiciousOperation
exception is raised when a user has
performed an operation that should be considered suspicious from a security
perspective, such as tampering with a session cookie. Subclasses of
SuspiciousOperation
include:
DisallowedHost
DisallowedModelAdminLookup
DisallowedModelAdminToField
DisallowedRedirect
InvalidSessionKey
RequestDataTooBig
SuspiciousFileOperation
SuspiciousMultipartForm
SuspiciousSession
TooManyFieldsSent
If a SuspiciousOperation
exception reaches the ASGI/WSGI handler level
it is logged at the Error
level and results in
a HttpResponseBadRequest
. See the logging
documentation for more information.
PermissionDenied
¶PermissionDenied
[sumber]¶Pengecualian PermissionDenied
dimunculkan ketika seorang pengguna tidak memiliki perizinan untuk melakukan tindakan diminta.
ViewDoesNotExist
¶ViewDoesNotExist
[sumber]¶Pengecualian ViewDoesNotExist
dimunculkan oleh django.urls
ketika tampilan diminta tidak ada.
MiddlewareNotUsed
¶MiddlewareNotUsed
[sumber]¶Pengecualian MiddlewareNotUsed
dimunculkan ketika sebuah middleware tidak digunakan dalam konfigurasi peladen.
ImproperlyConfigured
¶ImproperlyConfigured
[sumber]¶The ImproperlyConfigured
exception is raised when Django is
somehow improperly configured -- for example, if a value in settings.py
is incorrect or unparseable.
FieldError
¶FieldError
[sumber]¶Pengecualian FieldError
dimunculkan ketika ada masalah dengan bidang model. Ini terjadi untuk beberapa alasan:
ValidationError
¶ValidationError
[sumber]¶The ValidationError
exception is raised when data fails form or
model field validation. For more information about validation, see
Form and Field Validation,
Model Field Validation and the
Validator Reference.
RequestAborted
¶RequestAborted
[sumber]¶The RequestAborted
exception is raised when a HTTP body being read
in by the handler is cut off midstream and the client connection closes,
or when the client does not send data and hits a timeout where the server
closes the connection.
It is internal to the HTTP handler modules and you are unlikely to see it elsewhere. If you are modifying HTTP handling code, you should raise this when you encounter an aborted request to make sure the socket is closed cleanly.
SynchronousOnlyOperation
¶SynchronousOnlyOperation
[sumber]¶The SynchronousOnlyOperation
exception is raised when code that
is only allowed in synchronous Python code is called from an asynchronous
context (a thread with a running asynchronous event loop). These parts of
Django are generally heavily reliant on thread-safety to function and don't
work correctly under coroutines sharing the same thread.
If you are trying to call code that is synchronous-only from an
asynchronous thread, then create a synchronous thread and call it in that.
You can accomplish this is with asgiref.sync.sync_to_async()
.
Pengecualian Penyelesai URL ditentukan dalam django.urls
.
Resolver404
¶Resolver404
¶Pengeculian Resolver404
dimunculkan dengan resolve()
jika jalur dilewatkan ke resolve()
tidak memetakan ke tampilan. Itu adalah sebuah subkelas dari django.http.Http404
.
NoReverseMatch
¶NoReverseMatch
¶Pengecualian NoReverseMatch
dimunculkan dengan django.urls
ketika URL cocok dalam URLconf anda tidak dapat dicirikan berdasarkan pada parameter disokong.
Pengecualian basisdata mungkin diimpor dari django.db
.
Django membungkus pengecualian basisdata standar sehingga kode Django anda mempunyai jaminan penerapan umum pada kelas-kelas ini.
Error
¶InterfaceError
¶DatabaseError
¶DataError
¶OperationalError
¶IntegrityError
¶InternalError
¶ProgrammingError
¶NotSupportedError
¶Pembungkus Django untuk pengecualian basisdata berperilaku tepatnya sama seperti pengecualian basisdata pokok. Lihat:pep:249, Spesifikasi API Basisdata Python v2.0, untuk informasi lebih jauh.
As per PEP 3134, a __cause__
attribute is set with the original
(underlying) database exception, allowing access to any additional
information provided.
models.
ProtectedError
¶Raised to prevent deletion of referenced objects when using
django.db.models.PROTECT
. models.ProtectedError
is a subclass
of IntegrityError
.
models.
RestrictedError
¶Raised to prevent deletion of referenced objects when using
django.db.models.RESTRICT
. models.RestrictedError
is a subclass
of IntegrityError
.
Pengecualian Http mungkin diimpor dari django.http
.
UnreadablePostError
¶UnreadablePostError
¶UnreadablePostError
dimunculkan ketika pengguna membatalkan unggahan.
Pengecualian transaksi ditentukan dalam django.db.transaction
.
TransactionManagementError
¶TransactionManagementError
¶TransactionManagementError
dimunculkan untuk apapun dan semua masalah terkait pada transaksi basisdata.
Pengecualian disediakan oleh paket django.test
.
RedirectCycleError
¶client.
RedirectCycleError
¶RedirectCycleError
is raised when the test client detects a
loop or an overly long chain of redirects.
Django raises built-in Python exceptions when appropriate as well. See the Python documentation for further information on the Built-in Exceptions.
Apr 06, 2021