#26170: ModelAdmin add/change/delete views always run transaction on default
database
--------------------------------------+------------------------------------
Reporter: juntatalor | Owner: nobody
Type: Bug | Status: closed
Component: contrib.admin | Version: master
Severity: Normal | Resolution: fixed
Keywords: admin multi database | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"9459ec82aa12cad9b859c54c2f33f50bec057f2e" 9459ec8]:
{{{
#!CommitTicketReference repository=""
revision="9459ec82aa12cad9b859c54c2f33f50bec057f2e"
Fixed #26170 -- Made ModelAdmin views run transactions on the correct
database.
Thanks juntatalor for the initial patch.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26170#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.db4e4336d7824d12deb91dc86267ed89%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
