Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set USE_TZ=True #1838

Merged
merged 2 commits into from
Feb 12, 2025
Merged

set USE_TZ=True #1838

merged 2 commits into from
Feb 12, 2025

Conversation

alastair
Copy link
Member

Issue(s)
Closes #923

Description
With postgresql, this doesn't cause any issues with setting or retrieving data, even if the server and database server are set to different timezones.
In order to not compare offset-naive/aware timezones, always use django's timezone.now() method to get now.

Deployment steps:

With postgresql, this doesn't cause any issues with setting or
retrieving data, even if the server and database server are set to
different timezones.
In order to not compare offset-naive/aware timezones, always use
django's timezone.now() method to get now.
Make sure timezone aware dates are used in all fixtures and migrations
This was used before we added our new interface to bust caches for
static files
@ffont ffont merged commit 27b8004 into master Feb 12, 2025
1 check passed
@ffont ffont deleted the use-tz branch February 12, 2025 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable timezone support
2 participants