🐛 fix overriding table's short name #1981
Merged
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 problem is in these lines
metadata
refers to the same object and the secondtb_coverage.metadata.short_name
updates the short name of the first table, too. Functioncreate_dataset
, which accepts two tables, then overwrites the tables.I've added a uniqueness check for table short names and also fixed this by copying
metadata
object insidepd.read_csv
function.(Found this bug in our full rebuild.)