You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Django ORM executes "SELECT @@SQL_AUTO_IS_NULL" on the creation of a connection. When I use a connection pool, I expect to execute this query only on creation, not on every reuse of the connection.
Am I right? If not, what is the logic and why we need to call this query every time?
django's backend
Switch to django's backend (django.db.backends.xxx), does the problem reproduce?
Yes
Environment
Python Version: 3.10
Django Version: 3.1
Traceback
Post traceback here.
Optional: SQL and parameters
SELECT @@SQL_AUTO_IS_NULL
The text was updated successfully, but these errors were encountered:
Describe the bug
Django ORM executes "SELECT @@SQL_AUTO_IS_NULL" on the creation of a connection. When I use a connection pool, I expect to execute this query only on creation, not on every reuse of the connection.
Am I right? If not, what is the logic and why we need to call this query every time?
django's backend
Switch to django's backend (
django.db.backends.xxx
), does the problem reproduce?Yes
Environment
Traceback
Post traceback here.
Optional: SQL and parameters
SELECT @@SQL_AUTO_IS_NULL
The text was updated successfully, but these errors were encountered: