#16211: using negated F()-expression in update query
-------------------------------------+-------------------------------------
Reporter: wdoekes | Owner: nobody
Type: New feature | Status: reopened
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Ready for
Keywords: | checkin
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
Yeah, it is a little bit ugly that we need to use the bitwise operators
for their boolean meaning. But, that seems the only way forward if we want
to support boolean operators for F() expressions. And, it seems we want
that, this will allow using .update() in new situations with little added
code.
Even if we wouldn't want boolean operators for F() expressions it is
questionable if using '&' for different meaning in Q() and F() expressions
is a good API.
I believe the users of '&' and '|' in their bitwise meaning are extremely
rare, so this shouldn't be a big issue for most users.
I will commit the removal of '&' and '|' soon.
--
Ticket URL: <https://code.djangoproject.com/ticket/16211#comment:35>
Django <https://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 https://groups.google.com/groups/opt_out.
