#17755: Use database adapters for converting time zone aware datetimes in raw
queries
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: aaugustin
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version:
(models, ORM) | 1.4-beta-1
Severity: Release blocker | Resolution: fixed
Keywords: akaariai | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Aymeric Augustin <aymeric.augustin@…>):
In [changeset:"d9521f66b1851b0eacd55bc78f801dc64123e333" d9521f6]:
{{{
#!CommitTicketReference repository=""
revision="d9521f66b1851b0eacd55bc78f801dc64123e333"
Removed global timezone-aware datetime adapters.
Refs #23820.
Fixed #19738.
Refs #17755. In order not to introduce a regression for raw queries,
parameters are passed through the connection.ops.value_to_db_* methods,
depending on their type.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/17755#comment:8>
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/066.b2d8d97c172a801e8967f552153ad519%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
