Right now, if an object is deleted in the ORM, Django emulates ON
CASCADE DELETE behavior, and deletes "child" objects such that there
are no dangling foreign keys as a result of the delete.
Is there a way of delegating that to the database, and actually using
the database's own ON CASCADE DELETE?
--
-- 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.
