On 8/23/07, Gábor Farkas <[EMAIL PROTECTED]> wrote: > > hi, > > i posted this one week ago, could someone with commit access please > respond to it?
If we're haven't addressed these tickets, it's not because we don't want to - we have just had other priorities. Remember - we're all volunteers. On top of that, changes to the deletion code will be at least partially affected by changes to query.py, which is currently in the process of being refactored. This process has taken a little longer than originally intended (Malcolm keeps getting distracted by other fixes that people can't live without, like support for Oracle and unicode integration), so the tickets that are waiting on that refactor have been put on a bit of a hold. Of the tickets you mention, #2288 has the most complete description of the problem; however, as Malcolm mentions in the ticket, there are a lot of issues to consider with respect to how developers will be affected. There is a much bigger discussion that needs to happen around this topic - preferably when everyone isn't busy with something else :-) As for your specific suggestion - I'm -1 on 'interim' solutions to any problem becoming part of trunk. Once something is in trunk, we're making a commitment to support it long term. Introducing interim solutions just opens all sorts of nightmare situations where we are forced to support an API that we didn't really want in the first place. As you correctly noted, you can already do what you proposed without making any changes in trunk. You can override _collect_sub_objects or delete() to implement whatever behaviour you want. However, adding these changes to trunk would require making official API changes that might not be desirable in the light of a more comprehensive solution to the larger issues associated with #2288. So - Feel free to work up the patch you describe and circulate it, but I don't think it would be accepted to trunk. Alternatively, if you want to take a serious swing at the ON DELETE issue, we would welcome any contribution - but please be patient with the limited resources the core developers have to offer. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
