Hi Robert,
On 17 sept. 2014, at 01:54, Robert Rollins wrote:
> I have a legacy database from which my Django application must migrate data
> into a Django database. The relevant dates fields are actually TIMESTAMP
> columns in the database, but something (perhaps Django, or python's MySQL
> d
2014-09-18 23:29 GMT+02:00 Wim Feijen :
> Timezones confuse me, maybe Aymeric can answer this one if he has time?
>
I've bookmarked this thread to answer at some point but I have some
work-related matters to deal with first.
--
Aymeric.
--
You received this message because you are subscribed
Hi Robert,
On Tuesday, September 16, 2014 5:54:13 PM UTC-6, Robert Rollins wrote:
>
> I have a legacy database from which my Django application must migrate
> data into a Django database. The relevant dates fields are actually
> TIMESTAMP columns in the database, but something (perhaps Django, o
Hi Robert,
Timezones confuse me, maybe Aymeric can answer this one if he has time?
Off topic, your question might be a better fit for the django-users mailing
list, but perhaps you posted to django-developers intentionally, because
you are thinking of a bug report?
Wim
On Wednesday, 17 Sept
I have a legacy database from which my Django application must migrate data
into a Django database. The relevant dates fields are actually TIMESTAMP
columns in the database, but something (perhaps Django, or python's MySQL
driver?) loads these columns as timezone naive datetime objects, rather
