Django raises some of its own exceptions as well as standard Python exceptions.
\nKelas-kelas pengecualian inti django ditentukan dalam 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
TooManyFilesSent
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#Pengecualian PermissionDenied dimunculkan ketika seorang pengguna tidak memiliki perizinan untuk melakukan tindakan diminta.
ViewDoesNotExistLink to this heading#Pengecualian ViewDoesNotExist dimunculkan oleh django.urls ketika tampilan diminta tidak ada.
MiddlewareNotUsedLink to this heading#Pengecualian MiddlewareNotUsed dimunculkan ketika sebuah middleware tidak digunakan dalam konfigurasi peladen.
ImproperlyConfiguredLink to this heading#The ImproperlyConfigured exception is raised when Django is\nsomehow improperly configured -- for example, if a value in settings.py\nis incorrect or unparseable.
FieldErrorLink to this heading#Pengecualian FieldError dimunculkan ketika ada masalah dengan bidang model. Ini terjadi untuk beberapa alasan:
Sebuah bidang dalam sebuah model bertabrakan dengan sebuah bidang dari nama sama dari sebuah kelas dasar abstrak
Sebuah putaran tidak terbatasdisebutkan oleh pengurutan
Sebuah kata kunci tidak dapat diuraikan dari saringan prameter
Sebuah bidang tidak dapat ditentukan dari katakunci dalam parameter permintaan
Gabungan tidak diizinkan pada bidang tertentu
Nama bidang tidak sah
Sebuah permintaan mengandung argumen order_by tidak sah
ValidationErrorLink to this heading#The ValidationError exception is raised when data fails form or\nmodel field validation. For more information about validation, see\nForm and Field Validation,\nModel Field Validation and the\nValidator 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.
BadRequestLink to this heading#The BadRequest exception is raised when the request cannot be\nprocessed due to a client error. If a BadRequest exception reaches the\nASGI/WSGI handler level it results in a\nHttpResponseBadRequest.
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().
Pengecualian Penyelesai URL ditentukan dalam django.urls.
Resolver404Link to this heading#Pengeculian Resolver404 dimunculkan dengan resolve() jika jalur dilewatkan ke resolve() tidak memetakan ke tampilan. Itu adalah sebuah subkelas dari django.http.Http404.
NoReverseMatchLink to this heading#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.
\nPembungkus Django untuk pengecualian basisdata berperilaku tepatnya sama seperti pengecualian basisdata pokok. Lihat:pep:249, Spesifikasi API Basisdata Python v2.0, untuk informasi lebih jauh.
\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.
Pengecualian Http mungkin diimpor dari django.http.
UnreadablePostErrorLink to this heading#UnreadablePostError dimunculkan ketika pengguna membatalkan unggahan.
Eksepsi sesi ditentukan dalam django.contrib.sessions.exceptions.
SessionInterruptedLink to this heading#SessionInterrupted is raised when a session is destroyed in a\nconcurrent request. It's a subclass of\nBadRequest.
Pengecualian transaksi ditentukan dalam django.db.transaction.
TransactionManagementErrorLink to this heading#TransactionManagementError dimunculkan untuk apapun dan semua masalah terkait pada transaksi basisdata.
Pengecualian disediakan oleh paket django.test.
RedirectCycleErrorLink to this heading#RedirectCycleError is raised when the test client detects a\nloop or an overly long chain of redirects.
Django raises built-in Python exceptions when appropriate as well. See the\nPython documentation for further information on the Built-in Exceptions.
\n