Fix: Respect mssql_merge_exists flag and use merge as a strategy #5544
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.
A user reported that scd type 2 in python models don't respect
mssql_merge_exists
flag, but this is a more general issue. This is because this pr: #4531 addedDELETE+INSERT
strategy to be used instead ofMERGE
in_insert_overwrite_by_condition
for mssql. This update respects the flag if the user has opted in to use merge strategy for a particular model and usesmerge
instead.slack thread: https://tobiko-data.slack.com/archives/C044BRE5W4S/p1758704337222309