Hi, On Apr 3, 5:49 pm, meppum <[EMAIL PROTECTED]> wrote: > I have a simple parent child relationship. What i'm basically looking > to do is conditionally create a new child for a given parent anytime > that parent is modified in a certain way (certain fields). Should I > use signals for this or should I simply override the parents save > method and create the child there?
Both approaches are valid. The overridden save() approach is better if creation of those child objects is an integral part of your application's behaviour. If you foresee using this very same model/app in multiple projects where some projects won't need to create such child objects, then the signals approach allows you that flexibility in a cleaner way. -Rajesh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
