FIX: Remove SESSION timezone from LAMP_ALL_RT Query #203
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rymarczy
force-pushed
the
final-timestamp-lampt-rt-fix
branch
from
318f172
to
71949df
Compare
|
that is a nicer looking solution 🍰 |
mzappitello
approved these changes
Dec 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After consulting with the
#tid-eningeeringslack channel, this guide was provided (https://database.guide/how-at-time-zone-works-in-postgresql/) pointing me in the correct direction to make the LAMP_ALL_RT Query produced the same results no matter the SESSION timezone of the query runner.Instantiating a new timestamp object at a specified timezone is done with the following:
Creation of the
start_datetimeandstatic_start_datetimefields was also streamlined, convertingservice_datedirectly to a timestamp object (without a time zone) and then add seconds fromstart_timeorstatic_start_timeusing the postgresmake_intervalfunction.This should conclude the timestamp and time zone adventures in the LAMP_ALL_RT query, for now...