I had a need for this at one point because my main model had an overridden save method that would modify the inlines. But it didn't work because the inlines weren't there. I had to reverse the save method and put it on the inline model. But in my case, there was no reason not to do that.
:Marco On Jan 18, 8:14 am, Karen Tracey <kmtra...@gmail.com> wrote: > On Mon, Jan 18, 2010 at 6:23 AM, Gabriel Reis <gabriel...@gmail.com> wrote: > > In the ModelAdmin using inline forms I would like to know if it is possible > > to save the inline instances first/before saving the instance edited by the > > main ModelAdmin form. > > Why do you want to? > > It can't be done when you are adding a new main model, since the inlines > have a ForeignKey to the main model and the main model needs to have a > primary key (thus needs to have been saved) before the inlines can be > saved. (For changes it might could be made to work, but it is not the way > the admin code is written: it first saves the main model, then the inlines, > just as it does for adding.) > > Karen
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
