defined separately from the query’s parameters. Since parameters may be user-provided and therefore unsafe, they are escaped by the underlying database driver. Django also gives developers power to write enable ASGI mode if you have asynchronous code in your project. Async safety DJANGO_ALLOW_ASYNC_UNSAFE Certain key parts of Django are not able to operate safely in an async environment, as they have have global state that is not coroutine-aware. These parts of Django are classified as “async-unsafe”, and are protected from execution in an async environment. The ORM is the main example, but there are

defined separately from the query’s parameters. Since parameters may be user-provided and therefore unsafe, they are escaped by the underlying database driver. Django also gives developers power to write ASGI mode if you have asynchronous code in your project. 3.25.2 Async safety DJANGO_ALLOW_ASYNC_UNSAFE Certain key parts of Django are not able to operate safely in an async environment, as they have have global state that is not coroutine-aware. These parts of Django are classified as “async-unsafe”, and are protected from execution in an async environment. The ORM is the main example, but there are

defined separately from the query’s parameters. Since parameters may be user-provided and therefore unsafe, they are escaped by the underlying database driver. Django also gives developers power to write enable ASGI mode if you have asynchronous code in your project. Async safety DJANGO_ALLOW_ASYNC_UNSAFE Certain key parts of Django are not able to operate safely in an async environment, as they have have global state that is not coroutine-aware. These parts of Django are classified as “async-unsafe”, and are protected from execution in an async environment. The ORM is the main example, but there are

defined separately from the query’s parameters. Since parameters may be user-provided and therefore unsafe, they are escaped by the underlying database driver. Django also gives developers power to write enable ASGI mode if you have asynchronous code in your project. Async safety DJANGO_ALLOW_ASYNC_UNSAFE Certain key parts of Django are not able to operate safely in an async environment, as they have have global state that is not coroutine-aware. These parts of Django are classified as “async-unsafe”, and are protected from execution in an async environment. The ORM is the main example, but there are

defined separately from the query’s parameters. Since parameters may be user-provided and therefore unsafe, they are escaped by the underlying database driver. Django also gives developers power to write they have global state that is not coroutine-aware. These parts of Django are classified as “async-unsafe”, and are protected from execution in an asynchronous environment. The ORM is the main example, but to not call the offending code from an async context; instead, write your code that talks to async-unsafe in its own, synchronous function, and call that using asgiref.sync.sync_to_async(), or any other

defined separately from the query’s parameters. Since parameters may be user-provided and therefore unsafe, they are escaped by the underlying database driver. Django also gives developers power to write ASGI mode if you have asynchronous code in your project. 3.25.2 Async safety DJANGO_ALLOW_ASYNC_UNSAFE Certain key parts of Django are not able to operate safely in an async environment, as they have have global state that is not coroutine-aware. These parts of Django are classified as “async-unsafe”, and are protected from execution in an async environment. The ORM is the main example, but there are

defined separately from the query’s parameters. Since parameters may be user-provided and therefore unsafe, they are escaped by the underlying database driver. Django also gives developers power to write ASGI mode if you have asynchronous code in your project. 3.25.2 Async safety DJANGO_ALLOW_ASYNC_UNSAFE Certain key parts of Django are not able to operate safely in an async environment, as they have have global state that is not coroutine-aware. These parts of Django are classified as “async-unsafe”, and are protected from execution in an async environment. The ORM is the main example, but there are

defined separately from the query’s parameters. Since parameters may be user-provided and therefore unsafe, they are escaped by the underlying database driver. Django also gives developers power to write enable ASGI mode if you have asynchronous code in your project. Async safety DJANGO_ALLOW_ASYNC_UNSAFE Certain key parts of Django are not able to operate safely in an async environment, as they have have global state that is not coroutine-aware. These parts of Django are classified as “async-unsafe”, and are protected from execution in an async environment. The ORM is the main example, but there are

defined separately from the query’s parameters. Since parameters may be user-provided and therefore unsafe, they are escaped by the underlying database driver. Django also gives developers power to write enable ASGI mode if you have asynchronous code in your project. Async safety DJANGO_ALLOW_ASYNC_UNSAFE Certain key parts of Django are not able to operate safely in an async environment, as they have have global state that is not coroutine-aware. These parts of Django are classified as “async-unsafe”, and are protected from execution in an async environment. The ORM is the main example, but there are

defined separately from the query’s parameters. Since parameters may be user-provided and therefore unsafe, they are escaped by the underlying database driver. Django also gives developers power to write can also handle client disconnects in streaming responses. 3.25.2 Async safety DJANGO_ALLOW_ASYNC_UNSAFE Certain key parts of Django are not able to operate safely in an async environment, as they have have global state that is not coroutine-aware. These parts of Django are classified as“async-unsafe”, and are protected from execution in an async environment. The ORM is the main example, but there are