#13772: 'exists' parameter for pre_save signal
---------------------------------------------------+------------------------
          Reporter:  gsakkis                       |         Owner:  nobody
            Status:  reopened                      |     Milestone:  1.3   
         Component:  Database layer (models, ORM)  |       Version:  1.2   
        Resolution:                                |      Keywords:        
             Stage:  Design decision needed        |     Has_patch:  1     
        Needs_docs:  1                             |   Needs_tests:  0     
Needs_better_patch:  0                             |  
---------------------------------------------------+------------------------
Changes (by lrekucki):

  * stage:  Ready for checkin => Design decision needed

Comment:

 This ticket's history is a mess right now. You shouldn't mark your own
 patches as RFC. For starters, it still needs documentation. After that,
 they need to be reviewed by someone else.

 Also, based on [http://groups.google.com/group/django-
 developers/browse_frm/thread/3b5939ba089bce51/67892d99a9a6aff3 comment
 from Jeremy Dunck on django-dev], I'm not so sure we can just do this
 without cost. I'm going to push this back to DDN.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/13772#comment:8>
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-upda...@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.

Reply via email to