fix: EXPOSED-161 SQL Server syntax incorrectly allows CASCADE with dropSchema #1850
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.
When
SchemaUtils.dropSchema(schema, cascade = true)
is used with SQL Server it fails with the error:Documentation shows that CASCADE is not supported in this statement (from version 2016 upwards).
In fact, other uses of
dropSchema()
with cascade make sure to exclude SQL Server: