On Wed, Dec 10, 2008 at 12:59 PM, AcidTonic <[EMAIL PROTECTED]> wrote:
> > There is no anger here sir. I'm a rather sarcastic individual and I > guess there was a good dose there. > > I just cant for the life of me understand why this excellent framework > completely missed the point there. > > Is there a workaround that fixes the problem vs working around it? As > in a django patch/hack/fix as opposed to my code needing a change? > I've found that searching here: http://code.djangoproject.com/search for likely keywords (in this case I'd try "cascade") and reading the cited tickets, etc. is a good way to get a feel for the history of features that are perhaps non-obvious/surprising to me. (Also doing similar searches on the mailing lists can be useful.) I'll get a sense of whether it's just me or if there's been a lot of back-and-forth discussion and what influenced the way things are now. In this case as Joey already mentioned you'll find a ticket with a patch (that may not be current) that may be proposing the kind of thing you are looking for in the framework. You might want to evaluate that approach and see if it works for you, if not propose an alternative, etc. Karen --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
