Opened 13 years ago
Closed 10 years ago
#18931 closed New feature (wontfix)
Add predicate functionality to Q objects
| Reported by: | Preston Holmes | Owned by: | Preston Holmes |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description
A predicate is condition that can be matched against some item to determine whether that item meets the condition.
Django has a relatively rich set of lookup terms that can be used in filtering a queryset.
What is proposed is a new behavior of a Q object, that allows the conditions described in the formation of a Q instance, to be tested agains a model instance.
The initial implementation of this was released separately:
https://github.com/ptone/django-predicate
Current work-in-progress to bring this into Django is here:
https://github.com/ptone/django/compare/master...q-predicate
Change History (3)
comment:1 by , 13 years ago
| Has patch: | set |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 11 years ago
| Patch needs improvement: | set |
|---|
comment:3 by , 10 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
It seems like the improved lookups API has superseded this, at least for now.
Note:
See TracTickets
for help on using tickets.
This is now ready for more eyes to review
https://github.com/django/django/pull/388