On Nov 29, 1:17 pm, Luke Plant <l.plant...@cantab.net> wrote: > On 29/11/11 17:10, Paul Winkler wrote: > > > Hmm. I've been thinking of signals as key plug points for third-party > > apps, as well as a way to avoid needing database-specific stored > > procedures and triggers. Maybe I need to rethink that. > > Signals could be used for your use case, as an alternative to the method > I suggested - but it would be a *custom* signal provided by that app, > not one for QuerySet.update() itself.
Right, but you can only do that when "that app" is your own code. Lack of hooks like this is why I often find third-party apps unusable: there is no way to override or wrap small pieces of behavior without effectively rewriting the whole damn thing. So it goes ... thanks for the input anyway. - PW -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
