#12749: "Please correct the error below." when saving add model form with inline
formset and no auto primary key.
---------------------------------------------+------------------------------
Reporter: [email protected] | Owner: jkocherhans
Status: assigned | Milestone: 1.2
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by anonymous):
Replying to [comment:4 nessita]:
> * The design presented by the reporter doesn't seem to make sense,
since it generates a mutual dependency between the model ''Fashionista''
and ''ShoppingWeakness'': to create a ''Fashionista'', an instance of
''ShoppingWeakness'' is needed; and to create the latter, an instance of
''Fashionista'' is needed.
It's legal to create a Fashionista without !ShoppingWeakness (blank=True).
In fact, that's the only way to do it now: save the Fashionista, then
apply Weaknesses. The UI shortcut of having inline forms for the
Weaknesses is just broken.
This Unittest was "designed" just to point that out.
As for your little frustration.. I really relate to that. I bumped into
this
after some time without updating trunk. After a ''lot'' of weeding and
searching, I could boil it down to this example and part of changeset.
Fixing it was difficult cause the intention of [12206] wasn't really clear
to
me, and not fully documented/locked in a unittest.
It would still be very helpful if all of the model validation would have a
proper unittest so a rollback would break tests.
--
Ticket URL: <http://code.djangoproject.com/ticket/12749#comment:9>
Django <http://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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
