fix(sqllab): null database with backend persistence #19548
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
This PR fixes two problems in SQL Lab if the
SQLLAB_BACKEND_PERSISTENCE
feature flag is enabled (default as of 2.0):self.database
beingNone
SCRENSHOTS
When accessing SQL Lab with
SQLLAB_BACKEND_PERSISTENCE
turned on and a referenced database being missing, the following happens:After the above has been fixed and switching tabs into a tab where the database is missing, the following error toast is brought up:
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION