Set timezone to UTC in SQLAlchemy when connecting to PostgreSQL #3363
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.
Changes
Set timezone to UTC in SQLAlchemy when connecting to PostgreSQL
Issue
The fixes the following exception:
The cause is that when connecting to PostgreSQL that is configured with a different timezone than UTC (which as far as I know is normal when you run Debian packages of PostgreSQL), PostgreSQL returns the datetime with the configured timezone and the datetime gets serialized with a timezone. Specifying UTC as the timezone when connecting to PostgreSQL means we always get UTC back and resolves this problem.
QA notes
In docker the timezone is already UTC, so there shouldn't be any change when the standard docker development environment.
Checklist for code reviewers:
Copy-paste the checklist from the docs/source/templates folder into your comment.
Checklist for QA:
Copy-paste the checklist from the docs/source/templates folder into your comment.