sql: fix "descriptor not found" error when dropping a database with t… #67104
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.
…emp views
The bug here is that there are cases in drop database cascade where we'll
attempt to qualify the name of a view involved in a cascaded drop that is
not part of the current session's temporary schema. In that scenario, we
don't know the schema except by its ID. The temporary schemas do not have
descriptors, only namespace entries.
We could do something different like delete all of the views first but that
won't help for the backport PR we need to make as we only carry prefix
descriptors around in master.
Release note (bug fix): Fixed a bug where DROP DATABASE could return errors
if the database contained temporary views in use in an another session.