#10012: Query documentation uses objects.get with Q instead of objects.filter
------------------------------------+---------------------------------------
Reporter: jimpurbrick | Owner: nobody
Status: closed | Milestone:
Component: Documentation | Version: 1.0
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by mattmcc):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
This isn't a problem. Quoting that very documentation page:
"Each lookup function that takes keyword-arguments (e.g. filter(),
exclude(), get()) can also be passed one or more Q objects as positional
(not-named) arguments."
--
Ticket URL: <http://code.djangoproject.com/ticket/10012#comment:1>
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-updates@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
-~----------~----~----~----~------~----~------~--~---
