Opened 7 years ago

Closed 7 years ago

#10012 closed (invalid)

Query documentation uses objects.get with Q instead of objects.filter

Reported by: jimpurbrick Owned by: nobody
Component: Documentation Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description passes Q objects to objects.get, when it should pass them to objects.filter

Change History (1)

comment:1 Changed 7 years ago by mattmcc

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

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."

Note: See TracTickets for help on using tickets.
Back to Top