#26170: Admin.ModelAdmin incorrectly works with multiple databases
-------------------------------+----------------------------------
Reporter: juntatalor | Owner: nobody
Type: Bug | Status: new
Component: contrib.admin | Version: 1.9
Severity: Normal | Keywords: admin multi database
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+----------------------------------
When settings.DATABASES 'default' key is set to empty dict Django Admin
tries to perform transaction.atomic on dummy database, and it ends in
raising exception, when trying to change, add or delete record.
ModelAdmin functions that use transaction.atomic:
https://github.com/django/django/blob/master/django/contrib/admin/options.py#L1393
https://github.com/django/django/blob/master/django/contrib/admin/options.py#L1660
"using" argument (taken from db routers) should be specified for
transaction.atomic
Patch: https://github.com/django/django/pull/6076
--
Ticket URL: <https://code.djangoproject.com/ticket/26170>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.eca3602dc85e2a9b757e75ae552f692c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
