On Fri, Feb 20, 2009 at 1:49 AM, Michael Glassford <[email protected]> wrote: > > Just yesterday I updated the patch attached to > http://code.djangoproject.com/ticket/7539 so that it will apply against > the current version of Django (the previous patch required Django 0.96). > What are the chances of some form of this patch being included in one of > the next couple of versions of Django?
Now isn't the best time to be asking this sort of question. We're in the tail end of the v1.1 release cycle, and the everyone whose attention you need it concentrating on getting that release out the door. For 10c of personal opinion to tide you over: this is an area where improvement is both desirable and possible, but the final form of that improvement will require some design work. In this case, a big part of the design includes surveying the various database backends to establish the level of support for features like ON DELETE RESTRICT et al. If we expose a feature into the models and/or ORM, it will need to be supported (or emulated) across all the backends. The migration path from current behaviour to the new behaviour will also need to be very clear. However, now isn't the time for public discussions to sort out these details. If you want to do the research and get a proposal ready for the v1.2 proposal period, be my guest. 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 -~----------~----~----~----~------~----~------~--~---
