#36821: Asymmetry between exact and iexact when filtering for empty strings on
Oracle
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner:
| JaeHyuckSa
Type: Bug | Status: closed
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: iexact, | Triage Stage: Ready for
interprets_empty_strings_as_null | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"4ce4ed72a4ddc7d101df0fd31f1d0e449d8af501" 4ce4ed72]:
{{{#!CommitTicketReference repository=""
revision="4ce4ed72a4ddc7d101df0fd31f1d0e449d8af501"
Fixed #36821 -- Treated empty strings as NULL for iexact lookups on
Oracle.
Signed-off-by: JaeHyuck Sa <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36821#comment:5>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019bbdc6c80b-eacdabc4-4a7c-417a-8084-cb445bf81acd-000000%40eu-central-1.amazonses.com.
