EES-5056 Adding relationship from the Content DB's Files table to the Public API DB's DataSetVersion table #4739
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 ticket is to implement the database relationship so that CSV Datasets and Public API datasets can be linked - and then used across the Public API workstream.
The proposed solution is to add a new
PublicDataSetVersionId
column to theFiles
table in the Content DB. This links to the Id primary key in theDataSetVersions
table in the Public API DB.The
DataSetVersions
table in the Public API DB currently already has the inverse relationship in the form of aCsvFileId
column which corresponds to the Id primary key column of theFiles
table in the Content DB.