#35111: DateField's __range and __in lookups against expressions produce invalid
values on SQLite.
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"0fcee1676c7f14bb08e2cc662898dee56d9cf207" 0fcee16]:
{{{
#!CommitTicketReference repository=""
revision="0fcee1676c7f14bb08e2cc662898dee56d9cf207"
Fixed #35111 -- Fixed compilation of DateField __in/__range rhs on SQLite
and MySQL.
Also removed tests that ensured that adapt_(date)timefield backend
operations where able to deal with expressions when it's not the case
for any other adapt methods.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35111#comment:4>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d1168a176-3e19a12b-1c18-48af-8ec9-17f4b50f9279-000000%40eu-central-1.amazonses.com.
