On Apr 28, 2010, at 4:36 PM, dzida wrote:
"When Django deletes an object, it emulates the behavior of the SQL constraint ON DELETE CASCADE -- in other words, any objects which had foreign keys pointing at the object to be deleted will be deleted along with it. ", which is something I really want - but performed in shorter time.
I'm a bit surprised Django does this. Is there a reason that Django re-implements ON DELETE CASCADE for databases that support it?
-- -- Christophe Pettus x...@thebuild.com -- 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.
