feat: EXPOSED-486 Support REPLACE INTO ... SELECT clause #2199
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.
Description
Summary of the change:
Adds an overload for
replace()
that accepts a query as an argument, in the same way thatinsert()
can accept a query instead of column-value assignments.Detailed description:
It is already possible to generate SQL like INSERT INTO ... SELECT using
insert()
with a query parameter and REPLACE INTO ... VALUES is already supported byreplace()
. But it is not possible to generate REPLACE INTO ... SELECT without customizing the statement classes.It is now possible to generate this statement out of the box.
ReplaceSelectStatement
that extendsInsertSelectStatement
.Table.replace(query)
.Type of Change
Please mark the relevant options with an "X":
Affected databases:
Checklist
Related Issues
EXPOSED-486