Add unique constraint to last_run.command
#145
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
In b19ab98, the updating of the `last_run` table was migrated to Postgres-native logic by using `ON CONFLICT` to perform the update rather than an insert. This is a great change from the parent revision, but requires a unique constraint to be on `last_run.command` so that the update can actually occur.
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.
In b19ab98, the updating of the
last_runtable was migrated to Postgres-native logic by usingON CONFLICTto perform the update rather than an insert. This is a great change from the parent revision, but requires a unique constraint to be onlast_run.commandso that the update can actually occur.