cherry-pick 1.1: sql: revert the default behavior of DROP DATABASE to CASCADE #19209
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.
Cherry-pick of #19182.
... because that's what DROP DATABASE does in postgres, and schema
migration tools expect it to work this way.
However, in order to avoid unpleasant surprises by user, make
DROP DATABASE without behavior specifier also error out
when the session variable
sql_safe_updates
is set. This isthe case e.g. in interactive shells by default. For example:
cc @cockroachdb/release