Fix issue when using USE_TZ=False with MySQL #353
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
arrow always returns a tz aware datetime, and we don't want this when we explicitly configured Django with
USE_TZ=False
. This causes issues with MySQL (ERROR MySQL backend does not support timezone-aware datetimes when USE_TZ is False.
)This pull request makes the datetime object from arrow naive again when
USE_TZ=False
.This fixes #350 and #352