Bug #553: Baseline creates orphan version_id in ScriptsRun #567
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
When running in baseline mode, no SQL is actually run, so there was not inserted any entry into the Version table. However, this should be inserted in baseline mode, as this makes sense business-wise, to register the baseline as a version of the database (even with no changes) Fixes #553
erikbra
force-pushed
the
bugs/553-orphan-version_id
branch
from
9b744d8
to
90d3118
Compare
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.
When running in baseline mode, no SQL is actually run, so there was not inserted any entry into the Version table. However, this should be inserted in baseline mode, as this makes sense business-wise, to register the baseline as a version of the database (even with no changes)
Fixes #553