Baseline creates orphan version_id in ScriptsRun #553
Comments
|
That aligns with what i have observed, but maybe i have not understood what the baseline actually does? I assume that I would get a version row inside my grate.Version when using |
erikbra
added a commit
that referenced
this issue
Jul 24, 2024
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
added a commit
that referenced
this issue
Jul 24, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running baseline (SQL Server), while 'in progress' there is a new version in the grate.Version table, but on completion this has vanished, and the grate.ScriptsRun table is left with a set of entries with a non-existent version_id.
The version_id is then reused on the next grate run, so ScriptsRun ends up mixing Baseline and Update1 into one version_id, which is a bit confusing.
The text was updated successfully, but these errors were encountered: