#5780: pass the created/updated object to formsets in edit_inline for validation
--------------------------------------+-------------------------------------
Reporter: Honza_Kral | Owner: nobody
Status: new | Milestone: 1.0 alpha
Component: Admin interface | Version: newforms-admin
Resolution: | Keywords: nfa-blocker ep2008
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Comment (by jkocherhans):
Replying to [comment:8 Honza_Kral]:
> Replying to [comment:6 jkocherhans]:
> > Hey Honza... I may be dense here, but if you're using commit=False
when saving the forms, where do the objects get saved and will m2m fields
be saved? I wonder if we could use transaction.commit_manually here and
just roll the transaction back if any of the formsets fail validation.
Thoughts?
>
> I am the dense one here - the transaction-based approach would work
(with no problems), if you are willing to sacrifice MySQL MyISAM to get
there ;). That's your call
Grrr... if only I had a time machine so I could go back and... No. I
didn't think about that. It isn't an acceptable tradeoff. Damn my nice
tools altering my perception of reality! :)
--
Ticket URL: <http://code.djangoproject.com/ticket/5780#comment:9>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
