#35520: ModelAdmin uses incorrect database in change and delete views
-------------------------------+---------------------------------------
Reporter: Jake Howard | Owner: Jake Howard
Type: Bug | Status: assigned
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+---------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Accepted
Comment:
9459ec82aa12cad9b859c54c2f33f50bec057f2e was added to resolve #26170
through [https://github.com/django/django/pull/7143 !7143] where the point
of data inconsistencies was not brought up. I think it's fair that using
`db_for_read` for non-mutable HTTP requests was missed rather than
intentional.
--
Ticket URL: <https://code.djangoproject.com/ticket/35520#comment:2>
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/0107019008666d0f-bd348050-decb-472e-ae2c-002f76d99c25-000000%40eu-central-1.amazonses.com.
