feat: Support multiple values in SET
#36
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.
b098e2d added ability to set several comma-separated variables, e.g.
SET a = b, c = d
. This however came with a regression that does not allow setting several comma-separated values for a variable, e.g.SET a = b, c
.One case where this is problematic is
SET search_path = public, other_schema
with PostgreSQL. Such a query is issued, for instance, by DBeaver.This PR addresses the issue, allowing multiple values for a variable, instead of several variables (which is invalid syntax in Postgres) to be set when PostgreSQL or Redshift dialect is enabled.
Related test is included.