#31023: __second lookup doesn't work on Django 2.2.7.
-------------------------------------+-------------------------------------
Reporter: Ismael Jerez | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: query, filter, | Triage Stage:
datetimefield, second | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: new => closed
* resolution: => needsinfo
Comment:
Thanks for this report, however I'm not able to reproduce this issue. If
you use `USE_TZ = True` then it can be related with the lack of
[https://docs.djangoproject.com/en/2.2/ref/models/querysets/#database-
time-zone-definitions time zone definitions in the database]. Can you
provide more details or a sample project?
--
Ticket URL: <https://code.djangoproject.com/ticket/31023#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.0901a291696f517f141e49bc3cffd3e5%40djangoproject.com.
