#13677: ModelFormSet may query wrong database backend
-------------------------------------+-------------------------------------
Reporter: Pierre Chifflier | Owner: David
| Gouldin
Type: Bug | Status: closed
Component: Forms | Version: 1.2
Severity: Normal | Resolution:
| worksforme
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 Tobias Kunze):
* cc: rixx@… (added)
* needs_better_patch: 1 => 0
* has_patch: 1 => 0
* status: new => closed
* resolution: => worksforme
Comment:
I tried to build a ModelFormSet that uses the alternative database, and as
long as you specify for related objects to use the alternative database,
too, the validation is successful. (If you forget to specify the second
database, it throws a very explicit error stating that this model relation
is not possible).
My test case is avaliable here: https://github.com/rixx/django_ticket13667
- please provide a failing example if you want to reopen this ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/13677#comment:13>
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/064.49e195116faa087abb4deaf067dc5f21%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
