#17520: write queries on related managers use the db_for_read database
----------------------------------------------+--------------------
Reporter: tobias | Owner: nobody
Type: Bug | Status: new
Component: Database layer (models, ORM) | Version: 1.3
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
If you execute a write query (update() or delete()) on a queryset obtained
from a related manager, it appears to use the db_for_read database instead
of the db_for_write database for that query.
The attached patch reproduces the issue on trunk. It also exists in
1.3.1.
--
Ticket URL: <https://code.djangoproject.com/ticket/17520>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
