Currently second approach with update is implemented.
W dniu niedziela, 19 maja 2013 09:34:18 UTC+2 użytkownik Karol Sikora napisał: > > Hi, > > At djangocon sprints I implemented update_or_create method on QuerySet, > Patch is ready to merge on: https://github.com/django/django/pull/1132 > But after some discussion with folks here and on bugtracker, we need > design decision. > First approach is to following get_or_create approach, passing update part > of this method through models instances and calling save method on object. > Second approach is to use update method from QuerySet, and use 'create' > part of this method as someting like fallback. It allow us to update > multiple objects at the same time, and is probablu faster, but not calling > save on object has side effect - signals like post_create and so on wouldnt > be called. > > We need design decision which approach implement in update_or_create > method. > > Karol > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
