[21.05] Fix history audit table row trigger #12130
Merged
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
mvdbeek
force-pushed
the
legacy_postgres_testing
branch
3 times, most recently
from
a5c2d4d
to
7dd9066
Compare
mvdbeek
force-pushed
the
legacy_postgres_testing
branch
from
7dd9066
to
849ac16
Compare
nsoranzo
reviewed
Jun 11, 2021
Co-authored-by: Nicola Soranzo <nicola.soranzo@gmail.com>
mvdbeek
changed the title
|
This PR was merged without a "kind/" label, please correct. |
mvdbeek
changed the title
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.
The row trigger definition in postgres doesn't check for non-null values, failing on usegalaxy.eu.
I've changed the legacy paste API tests to run against postgresql 9.6, so that that branch is tested as well.
How to test the changes?
(Select all options that apply)
License