On 23 mar, 21:57, jrs <j...@framemedia.com> wrote: > Russ and Javier, > > Just to be clear... the reason for my initial note was due to my > already having a work queue which performs cleanup and maintains data > integrity. It is precisely due to this that I'm surprised the ORM has > cascading deletes on by default. Seems to me that cascades should > only happen when the app developer specifies, not the other way > around... it's dangerous and I'm certain that many developers were bit > by this.
Sorry to have to say the last part is pure nonsense. Preserving data integrity is of course the only sane default behaviour. How could NOT preserving data integrity be "dangerous" ??? looonng query ? And ? So what ? You are supposed to know your data model, don't you ? As for the "many developpers were bit by this", anyone in this situation is obviously not qualified to work as a programmer. Not in my team at least. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
