Bug #524: Scripts in internal Grate migration tables are always registered as "run" #566
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
…tered as "run" The running of the scripts to create the grate tables ScriptsRun, ScriptsRunErrors and Version were always run in baseline mode, even after the scripts had been registered as run, so they were registered as run every time (even if they were only run once).
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 running of the scripts to create the grate tables ScriptsRun, ScriptsRunErrors and Version were always run in baseline mode, even after the scripts had been registered as run, so they were registered as run every time (even if they were only run once).
Fixes #524