#23420: Custom lookup transformers can't create DateTimeFields when USE_TZ=True
-------------------------------------+-------------------------------------
Reporter: chosak | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.7
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage: Accepted
Keywords: lookup, transform, | Needs documentation: 0
datetimefield | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Anssi Kääriäinen <akaariai@…>):
In [changeset:"12e5b87b89074cd0380ddcdadd24a6c621178c07"]:
{{{
#!CommitTicketReference repository=""
revision="12e5b87b89074cd0380ddcdadd24a6c621178c07"
[1.7.x] Fixed #23420 - broken warning for unbound naive datetime objects
Fixed issue with warning message displayed for unbound naive datetime
objects when USE_TZ is True. Adds unit test that demonstrates the issue
(discoverable when using a custom lookup in MySQL).
Backport of ceb1ffcc8d from master.
Conflicts:
tests/custom_lookups/tests.py
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23420#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.d8bc5ca9e59ecb18bb3c15bb2321d99c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
