#28410: query filter on date portion of datetime creates wrong parameters for mysql CONVERT_TZ function and returns no results -------------------------------------+------------------------------------- Reporter: donaldinho | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: 1.11 (models, ORM) | Severity: Normal | Resolution: Keywords: timezone date | Triage Stage: Accepted filter | Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Tim Graham):
* stage: Unreviewed => Accepted Comment: I can reproduce the problem, although poking around the code left me wondering if there's a reason not to deprecate `get_fixed_timezone()` and `FixedOffset` so we don't have to handle this additional case. Is there a reason you're preferring that rather than using `pytz`? I didn't see an explanation of the `get_fixed_timezone()`'s use case in Django's documentation. -- Ticket URL: <https://code.djangoproject.com/ticket/28410#comment:2> 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 post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/068.d29750ecfa77137491e19372f5a79af1%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.