#30865: Document that some DATABASES['OPTIONS'] are not passed to dbshell
database
shell.
-------------------------------------+-------------------------------------
Reporter: Simon | Owner: nobody
Charette |
Type: | Status: new
Cleanup/optimization |
Component: | Version: master
Documentation | Keywords: dbshell database
Severity: Normal | options
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
Some of `DATABASES['OPTIONS']` (e.g.
[https://docs.djangoproject.com/en/2.2/ref/databases/#isolation-level
isolation_level]) are not passed to the the underlying shell.
In the long run I think we should try to add support for as many as of
them as possible but since this will likely require and some time and
discussion we should at least document the limitation.
For context, we spent a good amount of trying to figure out why `SELECT
@@TX_ISOLATION` was returning a `REPEATABLE-READ` while we had set
`isolation_level = 'read committed'` in our `OPTIONS`.
I think it might be more discoverable if the a note was added beside
`DATABASES['OPTIONS']` instead of `dbshell`` as that's where we initially
looked but that's just anecdotal evidence.
--
Ticket URL: <https://code.djangoproject.com/ticket/30865>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.aa3a469bc7c88ee4e04232012cd38e6c%40djangoproject.com.
