Django 3.0.x Documentationregister_converter() django.conf.urls functions for use in URLconfs static() url() handler400 handler403 handler404 handler500 Django Utils django.utils.cache django.utils.dateparse django.utils.decorators ) will already have been rolled back safely when handle_exception() is called, so the exception handler can also operate on the database if necessary. Avoid catching exceptions inside atomic! When exiting raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block as shown0 码力 | 3085 页 | 2.95 MB | 1 年前3- Django 4.2.x Documentationinclude() register_converter() django.conf.urls functions for use in URLconfs static() handler400 handler403 handler404 handler500 Django Utils django.utils.cache django.utils.dateparse django.utils.decorators ) will already have been rolled back safely when handle_exception() is called, so the exception handler can also operate on the database if necessary. Avoid catching exceptions inside atomic! When exiting raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block as shown0 码力 | 3305 页 | 3.16 MB | 1 年前3
- Django 4.1.x Documentationinclude() register_converter() django.conf.urls functions for use in URLconfs static() handler400 handler403 handler404 handler500 Django Utils django.utils.cache django.utils.dateparse django.utils.decorators will already have been rolled back safely when handle_exception() is called, so the exception handler can also operate on the database if necessary. Avoid catching exceptions inside atomic! When exiting raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block as shown0 码力 | 3240 页 | 3.13 MB | 1 年前3
- Django 4.0.x Documentationinclude() register_converter() django.conf.urls functions for use in URLconfs static() handler400 handler403 handler404 handler500 Django Utils django.utils.cache django.utils.dateparse django.utils.decorators will already have been rolled back safely when handle_exception() is called, so the exception handler can also operate on the database if necessary. Avoid catching exceptions inside atomic! When exiting raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block as shown0 码力 | 3184 页 | 3.14 MB | 1 年前3
- Django 2.1.x Documentationregister_converter() django.conf.urls functions for use in URLconfs static() url() handler400 handler403 handler404 handler500 Django Utils django.utils.cache django.utils.dateparse django.utils.decorators ) will already have been rolled back safely when handle_exception() is called, so the exception handler can also operate on the database if necessary. Avoid catching exceptions inside atomic! When exiting raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block as shown0 码力 | 2790 页 | 2.71 MB | 1 年前3
- Django 2.2.x Documentationregister_converter() django.conf.urls functions for use in URLconfs static() url() handler400 handler403 handler404 handler500 Django Utils django.utils.cache django.utils.dateparse django.utils.decorators ) will already have been rolled back safely when handle_exception() is called, so the exception handler can also operate on the database if necessary. Avoid catching exceptions inside atomic! When exiting raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block as shown0 码力 | 2915 页 | 2.83 MB | 1 年前3
Django 2.1.x Documentation) will already have been rolled back safely when handle_exception() is called, so the exception handler can also operate on the database if necessary. Avoid catching exceptions inside atomic! When exiting raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block as shown are: • handler400 – See django.conf.urls.handler400. • handler403 – See django.conf.urls.handler403. • handler404 – See django.conf.urls.handler404. • handler500 – See django.conf.urls.handler500. Including0 码力 | 1910 页 | 6.49 MB | 1 年前3- Django 4.0.x Documentation) will already have been rolled back safely when handle_exception() is called, so the exception handler can also operate on the database if necessary. Avoid catching exceptions inside atomic! When exiting raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block as shown are: • handler400 – See django.conf.urls.handler400. • handler403 – See django.conf.urls.handler403. • handler404 – See django.conf.urls.handler404. • handler500 – See django.conf.urls.handler500. 2080 码力 | 2248 页 | 7.90 MB | 1 年前3
- Django 2.0.x Documentationregister_converter() django.conf.urls functions for use in URLconfs static() url() handler400 handler403 handler404 handler500 Django Utils django.utils.cache django.utils.dateparse django.utils.decorators ) will already have been rolled back safely when handle_exception() is called, so the exception handler can also operate on the database if necessary. Avoid catching exceptions inside atomic! When exiting raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block as shown0 码力 | 2746 页 | 2.67 MB | 1 年前3
- Django 1.8.x Documentationget_script_prefix() django.conf.urls utility functions patterns() static() url() include() handler400 handler403 handler404 handler500 Django Utils django.utils.cache django.utils.datastructures django.utils.dateparse ) will already have been rolled back safely when handle_exception() is called, so the exception handler can also operate on the database if necessary. Avoid catching exceptions inside atomic! When exiting raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block as shown0 码力 | 2454 页 | 2.85 MB | 1 年前3
共 65 条
- 1
- 2
- 3
- 4
- 5
- 6
- 7