#9094: Invoke method after create_update.(create|update|delete)_object methods
------------------------------------+---------------------------------------
Reporter: das | Owner: nobody
Status: closed | Milestone:
Component: Generic views | Version: 1.0
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
This seems to be making things more and more complicated in generic view
land. It's getting to the point that they're effectively unusable because
of the many, many parameters that form their own little language of
configuration.
You can already achieve this result with a signal handler on the post_save
and post_delete signals for the appropriate models. So let's not add
another way to do the same thing.
--
Ticket URL: <http://code.djangoproject.com/ticket/9094#comment:3>
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 [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
-~----------~----~----~----~------~----~------~--~---
