RFC: #30053 Allow for conditional QuerySet.update_or_create()

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 prop

Re: BitBounce Spam Replies From the Mailing List

I just got one for $2.00. So I assume either the two original "bouncers" fixed their settings and we have a new "bouncer" or one of them changed their dollar amount. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself

Re: BitBounce Spam Replies From the Mailing List

Nevermind, got the $999.99 reply as well :) On Friday, December 28, 2018 at 10:23:07 AM UTC-6, Joshua Cannon wrote: > > I just got one for $2.00. So I assume either the two original "bouncers" > fixed their settings and we have a new "bouncer" or one of them c

Re: RFC: #30053 Allow for conditional QuerySet.update_or_create()

value of a previous get_or_create >> with a >> bit of boilerplate[0] pushes me to a -1 because I don't think it's a >> common enough >> pattern to warrant the addition of a specialized option. >> >> Cheers, >> Simon >> >> [0] htt