SQLite3 backend raises error when reading tz-aware datetime value

[Ryo Chijiiwa]

When a DateTimeField in a sqlite3 backend contains a timezone-aware value, an error is raised when reading the object. This seems to happen because ​convert_datetimefield_value doesn't check to make sure the value is naive before passing to make_aware, which ​raises an error if it receives a tz-aware value.

[Kenneth]

SQLite doesn't support tz-aware datetimes.

[Ryo Chijiiwa]

I have a bit of code (a unit test) that works in Django 1.7 and 1.8, but breaks in 1.9. Both 1.7 and 1.8 check the value to see if it's tz-naive (​here and ​here) but not 1.9. Am I to interpret that this change in behavior is by design?

[Kenneth]

I think an exception is the desired behavior when trying to read a tz-aware value from a db that doesn't support timezone. Here are more info I found about this change: ​here and ​here

Replying to ryochiji:

I have a bit of code (a unit test) that works in Django 1.7 and 1.8, but breaks in 1.9. Both 1.7 and 1.8 check the value to see if it's tz-naive (​here and ​here) but not 1.9. Am I to interpret that this change in behavior is by design?