#2288: Provide an equivalent for 'ON DELETE' and friends
---------------------------+------------------------------------------------
Reporter: ubernostrum | Owner: adrian
Status: new | Component: Core framework
Version: | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------+------------------------------------------------
Comment (by mtredinnick):
When we come up with a reasonable solution for this, we also need to work
out how this is going to impact developers. If they try to delete an
object and cascading deletes aren't enabled, will the developer be
responsible for cacthing the !IntegrityError, or will that be handled by
the delete_object code?
No opinion on this yet, just transferring the issue from #1320 so I can
close that off.
--
Ticket URL: <http://code.djangoproject.com/ticket/2288#comment:8>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
