[Django] #21552: Cannot use None as a query value for iexact lookup
Django
----------------------------------------------+--------------------
Reporter: denya | Owner: nobody
Type: Bug | Status: new
Component: Database layer (models, ORM) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
----------------------------------------------+--------------------
Current behavior is "None is interpreted as an SQL NULL, but only in exact
queries."
'''i'''exact=None lookup fails now. It's wrong behavior.
iexact=None lookup must behave like exact=None query.
--
Ticket URL: <https://code.djangoproject.com/ticket/21552>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: denya | Owner: nobody
Type: Bug | Status: new
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
Changes (by denya):
* needs_docs: => 0
* has_patch: 0 => 1
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
See the pull request, please:
https://github.com/django/django/pull/2020
--
Ticket URL: <https://code.djangoproject.com/ticket/21552#comment:1>
Django
Reporter: denya | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Keywords: | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Changes (by timo):
* needs_docs: 0 => 1
* type: Bug => New feature
* stage: Unreviewed => Accepted
Comment:
I'm not sure if `iexact` was intentionally omitted when the feature for
`exact` was added in the [https://github.com/django/django/commit/9c52d56f
#django-db-models-sql-query-py-P919 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).
--
Ticket URL: <https://code.djangoproject.com/ticket/21552#comment:2>
Django
Reporter: denya | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
* cc: anubhav9042 (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/21552#comment:3>
Django
Reporter: denya | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by anubhav9042):
See the pull request please:
https://github.com/django/django/pull/2088
--
Ticket URL: <https://code.djangoproject.com/ticket/21552#comment:4>
Django
Reporter: denya | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: master
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"d4e578d0f64971483ded49f9cae460ea174b5138"]:
{{{
#!CommitTicketReference repository=""
revision="d4e578d0f64971483ded49f9cae460ea174b5138"
Fixed #21552 -- Allowed the use of None for the iexact lookup.
Thanks Anubhav Joshi for the documentation.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21552#comment:5>