Highlight missing PostgreSQL upgrade scripts - #8138
Open
labkey-adam wants to merge 4 commits into
Open
labkey-adam wants to merge 4 commits into
labkey-adam wants to merge 4 commits into
Conversation
labkey-adam
requested review from
labkey-bpatel,
labkey-jeckels and
labkey-martyp
October 5, 2026 22:48
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Rationale
We want to notice when SQL Server upgrade scripts are added without corresponding PostgreSQL scripts
Changes
core.fn_dropifexiststo the migrate and clean up script actions so they know what the proc does and how to replace it. There are no core.fn_dropifexists calls in develop, but they could sneak in on 26.3 or 26.7.