Correct syntax errors in database upgrade to 1.15.0 #132
Conversation
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
- Correct the syntax errors that occur when removing (upgrade) or restoring (backout) the "NOT NULL" constraint on the "target" column in the "hostlink" table. - This commit addresses issue quattor#131 Change-Id: I86c5a8d4d09c5becfc545b2dcb557e831d30c275
joaocosta
pushed a commit
to joaocosta/aquilon
that referenced
this pull request
Jan 13, 2025
Merge in AQUILON_AQD/aqd from ~KAMURTHY/aqd:Bug/AQUILONAQD-1225/Exclude_Ring1_From_RO_Batch to master * commit '741b417d061f5d3e8028b8aab7b587255c20357a': AQUILONAQD-1225/Exclude_Ring1_From_RO_Batch
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.
Corrects the syntax errors that occur when removing (upgrade) or restoring (backout) the "NOT NULL" constraint on the "target" column in the "hostlink" table for the postgresql DBMS. From a quick consultation with Dr. Google, the Oracle DBMS syntax appears to be correct.
This addresses issue issue #131
Change-Id: I86c5a8d4d09c5becfc545b2dcb557e831d30c275