, reverting it would be particularly vexing for
> affected
> > users who updated their code.
> >
> > To sum up, the question we’re reaching is:
> >
> > “When USE_TZ =True, should cursor.execute() with a Django cursor return
> (a)
> > naive datetim
Also to directly answer the question, I'm talking abour cursor.execute()
On Thursday, April 28, 2016 at 3:48:21 PM UTC-7, Bryce Drennan wrote:
>
> I'm wondering if we're using the term "global" slightly differently.
>
> Yes, prior to the changes removing converters, Djang
Carl in the mailing list thread, if you’re having a
> problem with `cursor.execute()`, the easiest solution is to reinstall
> yourself the same global converter Django used to install. Is that what you
> meant by “monkey-patching Django”?
>
> --
> Aymeric.
>
> On 20 Apr 2016, a
timezone aware datetimes for mysql, thus saving us from manually fixing
many many queries. Is this a bad plan? Is there a better way?
Thank you,
Bryce Drennan
Senior Engineer @ Circleup
References
1.
https://code.djangoproject.com/ticket/19738 - "manage.py shell" on a
fre
