fix(dataset): handle missing sqla uri in migration #20073
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.
SUMMARY
When running the migration
a9422eeaae74_new_dataset_models_take_2.py
from #19421 I ran into a problem where some old faulty database metadata caused the migration to fail. This adds a check for the truthiness ofdrivername
similar to what's done a few rows above:superset/superset/migrations/versions/a9422eeaae74_new_dataset_models_take_2.py
Line 577 in 1c3c3ae
BEFORE
AFTER
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION