#7539: Add ON DELETE and ON UPDATE support to Django
---------------------------------------------------+------------------------
Reporter: glassfordm | Owner:
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords: feature
Stage: Design decision needed | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by emulbreh):
Changes between 7539.on_delete.diff and 7539.on_delete.r11706.diff:
* Added tests.
* Replaced class based constants with callables that do what
`_handle_sub_object()` did before. That cleans up `_collect_sub_objects()`
and allows `on_delete` behaviors to be added without touching any existing
code (I added `on_delete=SET(value)`, because it's just a four line
utility function).
* Merged `CollectedFields` into `CollectedObjects`
* Made all operations that require knowledge of internals methods on
`CollectedObjects`. This makes `django.db.models.base.delete_objects` more
readable.
* Couldn't resist and rewrote parts of `CollectedObjects`.
--
Ticket URL: <http://code.djangoproject.com/ticket/7539#comment:29>
Django <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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
