Howdy folks!

At the suggestion of Simon Charette, I'd like to get feedback on how the 
community feels about the feature request #30053 
The gist of the problem is that sometimes the "update" part of 
"update_or_create" should be conditional. The proposed solution adds a 
backwards-compatible "update_condition" parameter to "update_or_create" 
which should be a unary callable that takes in the retrieved table instance 
and returns a boolean of whether the update should be performed.

Nasir Hussain has already started work on a possible solution on PR 10800 

I'd love to hear other people's thoughts.

You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

Reply via email to