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, or
> python's MySQL driver?) loads these columns as timezone naive datetime
> objects, rather than integers. So I wrote my migration code under the
> assumption that the dates coming out of the legacy database are timezone
> naive.
>
> Unfortunately, now that I'm trying to write tests for this migrator, I
> can't find any way to load timezone naive datetimes into my test legacy
> database. I can't use integer timestamps, because the DateTimeField doesn't
> accept that kind of input (I get a JSON serialization error when I try), so
> I'm using datetime strings like this: "2014-08-01T00:00:00" in my fixture.
> But
> regardless of whether or not I include a UTC offset in the string, the
> datetime objects that come out of the database during my tests are somehow
> timezone aware. This causes my code to crash because it calls make_aware(),
> which throws ValueError('Not naive datetime (tzinfo is already set)').
>
> It seems like having USE_TZ = True is forcibly making my fixture dates
> timezone aware, which I don't want. But USE_TZ will be True during the
> actual migration, so I can't just turn it off during the tests. So how can
> I load timezone naive dates into my test database?
>
I think your analysis is correct; USE_TZ = True does enforce that only
aware datetimes are saved to the database, by design.
I'm not immediately thinking of a better approach for your situation than
to load your test data into the source database via raw SQL inserts rather
than via Django's fixture mechanism.
--
You received this message because you are subscribed to the Google Groups
"Django developers" 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].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/c7d86520-32e1-4f57-afed-827955cd3550%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
