-
Notifications
You must be signed in to change notification settings - Fork 887
fix(coderd/database): migrate workspaces.last_used_at to timestamptz #9699
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
0fedbd3
fix(coderd/database): migrate workspaces.last_used_at to timestamptz
johnstcn 0fcfe57
stop using utc loc in test
johnstcn d5babdf
stop using utc loc in test
johnstcn cd580fb
fixup! stop using utc loc in test
johnstcn 19663d7
Merge remote-tracking branch 'origin/main' into cj/workspaces-last-us…
johnstcn 939938e
Merge remote-tracking branch 'origin/main' into cj/workspaces-last-us…
johnstcn 8953f64
Merge remote-tracking branch 'origin/main' into cj/workspaces-last-us…
johnstcn 672f3e1
Merge remote-tracking branch 'origin/main' into cj/workspaces-last-us…
johnstcn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
fix(coderd/database): migrate workspaces.last_used_at to timestamptz
- Loading branch information
commit 0fedbd3bfc6fd215ece6c9e37afffb4e9838ccd9
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
6 changes: 6 additions & 0 deletions
6
coderd/database/migrations/000155_workspaces_last_used_at_timestamptz.down.sql
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
ALTER TABLE ONLY workspaces | ||
ALTER COLUMN last_used_at | ||
SET DATA TYPE timestamp | ||
USING last_used_at::timestamptz, | ||
ALTER COLUMN last_used_at | ||
SET DEFAULT '0001-01-01 00:00:00'::timestamp; |
6 changes: 6 additions & 0 deletions
6
coderd/database/migrations/000155_workspaces_last_used_at_timestamptz.up.sql
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
ALTER TABLE ONLY workspaces | ||
ALTER COLUMN last_used_at | ||
SET DATA TYPE timestamptz | ||
USING last_used_at::timestamp AT TIME ZONE 'UTC', | ||
ALTER COLUMN last_used_at | ||
SET DEFAULT '0001-01-01 00:00:00+00:00'::timestamptz; |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we want to be 100% correct, this could use an
AT TIME ZONE 'UTC'
too because during the up migration we are changing the time (correctly) if the db time zone is non-UTC.This demonstrates how the timestamp would be coerced into the wrong time without
Whereas with the time zone change:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated!