Am 16.11.2012 18:17, schrieb Martin J. Laubach:
Don't overthink it.
If believe you are likely to run into cascading recursive updates,
then those cascades will happen no matter where you put the update. You
will need to deal with it some way or another (locking, careful
ordering, better data structures, whatever), but just moving things
around will not automatically clean up the mess :-)
Uh, why? I don't try to move things around, but just to separate them to
remove any complexity:
I want to have the admin interface save the inline models, and when that
is done, post-process / update them as required.
The only key piece that I'm missing is where to hook into the admin for
that purpose?
The documentation mentions several methods that look promising, e.g.
ModelAdmin.save_model()
ModelAdmin.save_formset()
ModelAdmin.save_related()
but unfortunately says nothing about their purpose, or the context or
the order that they're called in.
Best regards,
Carsten
--
Cafu - the open-source Game and Graphics Engine
for multiplayer, cross-platform, real-time 3D Action
Learn more at http://www.cafu.de
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@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.
