Opened 12 years ago
Closed 12 years ago
#21552 closed New feature (fixed)
Cannot use None as a query value for iexact lookup
| Reported by: | Denis Moskalets | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | ANUBHAV JOSHI | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | yes |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
Current behavior is "None is interpreted as an SQL NULL, but only in exact queries."
iexact=None lookup fails now. It's wrong behavior.
iexact=None lookup must behave like exact=None query.
Change History (5)
comment:1 by , 12 years ago
| Has patch: | set |
|---|
comment:2 by , 12 years ago
| Needs documentation: | set |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
| Type: | Bug → New feature |
I'm not sure if iexact was intentionally omitted when the feature for exact was added in the QuerySet refactor branch, but I don't see a reason not to have it.
It would be good to update the documentation (.. verisonchanged:: for iexact and a mention in the release notes).
comment:3 by , 12 years ago
| Cc: | added |
|---|
comment:4 by , 12 years ago
See the pull request please:
https://github.com/django/django/pull/2088
comment:5 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
See the pull request, please:
https://github.com/django/django/pull/2020