On Fri, Dec 12, 2008 at 2:48 AM, James Bennett <ubernost...@gmail.com> wrote: > > On Thu, Dec 11, 2008 at 7:06 PM, Simon Litchfield <si...@slicmedia.com> wrote: >> +1. Definitely need some kind of cascade=False option somewhere. I'd >> argue it should be the default. I have some production horror stories >> which I'm sure I don't need to share. > > Keep in mind there is some prior art here which may be useful to review: > > http://groups.google.com/group/django-developers/msg/4c65ac76d85c5c34 >
there is an other usecase, that was maybe not considered yet: sometimes the program has to decide dynamically if a delete should run with-cascade or without-cascade. for example, in a web-application, when an user clicks on deleting something, an user with administrator privileges should be able to delete the object (and the system will cascade-delete everything around it, preferably by first showing a warning message to the user), but an user without admin privileges should just get an error-message. currently there's just no way to do this cleanly in django from the "client" side (i mean without modifying django) gabor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
