-
Notifications
You must be signed in to change notification settings - Fork 11.7k
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
Unified Storage: create kind_version table migration, add SQL and fix db #87977
Unified Storage: create kind_version table migration, add SQL and fix db #87977
Conversation
613933c
to
b5c8432
Compare
@@ -0,0 +1,59 @@ | |||
package dbimpl |
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.
We need these changes to be able to execute in different isolation levels.
LIMIT 1 | ||
{{ end }} | ||
|
||
{{ if .SelectForUpdate }} |
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.
from pairing session: add no wait
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.
Will be added in the followup PR.
( | ||
{{ .Ident "group" }}, | ||
{{ .Ident "resource" }}, | ||
{{ .Ident "resource_version" }} |
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.
from pairing session: possibly add updated_at
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.
Fixed! Added created_at
as well for completeness, doesn't hurt and might be useful in the future. Note that I cannot add the proper DEFAULT
to set the current timestamp because that is SQL-Dialect dependent, so I will change the corresponding SQL templates in the upcoming PRs.
What is this feature?
kind_version
table.Why do we need this feature?
To implement Proposal 1 for Consistent Resource Version.
Who is this feature for?
Everyone
Which issue(s) does this PR fix?:
None
Special notes for your reviewer:
Please check that: