Remove the column reordering tool and the schema structure validations #16488
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
Version 2.0 and greater of pglogical doesn't require that the columns of a replicated table be in the same order on the source and destination databases. All of this was written to guard against and correct this situation so now it can be removed. ref: 2ndQuadrant/pglogical@88ff7ff
|
Checked commit carbonin@eaefbd0 with ruby 2.3.3, rubocop 0.47.1, haml-lint 0.20.0, and yamllint 1.10.0 **
|
|
😍 |
simaishi
pushed a commit
that referenced
this pull request
Nov 17, 2017
…er_checks Remove the column reordering tool and the schema structure validations (cherry picked from commit 5deab50)
|
Gaprindashvili backport details: |
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.
Version 2.0 and greater of pglogical doesn't require that the columns of a replicated table be in the same order on the source and destination databases.
All of this was written to guard against and correct this situation so now it can be removed.
Related schema PR ManageIQ/manageiq-schema#129
ref: 2ndQuadrant/pglogical@88ff7ff