#10672: Proxy Model does not send save signal
---------------------------------------------------+------------------------
Reporter: zbyte64 | Owner: nobody
Status: new | Milestone: 1.1
Component: Database layer (models, ORM) | Version: 1.1-beta-1
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by k0001):
* cc: gnuk0...@gmail.com (added)
* has_patch: 0 => 1
* stage: Accepted => Design decision needed
Comment:
I've attached a patch that fixes this issue. Notice we must carry around
the value for the "created" argument of the signal: I thought the cleanest
(and probably useful) way to do this could be to add a return value to
save_base as the patch shows.
Thoughts:
Shouldn't we send both {{{sender=Test1Model}}} and
{{{sender=TestProxyModel}}} post_save signals in a situation like the one
on the given example? If we take this approach, in what order should we
send the signals?
--
Ticket URL: <http://code.djangoproject.com/ticket/10672#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
