EES-4993 Move PublicApiDataSet*
columns from Files
to ReleaseFiles
#4979
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.
This PR moves the
PublicApiDataSetId
andPublicApiDataSetVersion
columns from the content DB'sFiles
table toReleaseFiles
.This fixes an issue where creating a draft API data set for a
ReleaseFile
in an amendment can immediately show in the Data Catalogue as an API data set. This was due to thePublicApiDataSet*
columns previously being on theFiles
table, meaning any changes would be shared between allReleaseFiles
sharing the sameFile
.PublicApiDataSet*
columns for any amendmentReleaseFiles
that have already been created with this issue.