Return an error when multiple rows are returned from a scalar subquery #13514
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.
Implements #11521
Implements #13469
This PR modifies the behavior of scalar subqueries so that an error is thrown when multiple rows are returned, instead of returning a random row. This aligns the behavior of the system with that of Postgres, instead of that of SQLite.
For example:
The old behavior is available through the
scalar_subquery_error_on_multiple_rowsconfiguration setting: