Skip to content

Conversation

@QMalcolm
Copy link

resolves #204

Description

Previously what was being used was dbt.default_get_delete_insert_merge_sql. This always got the "default" delete insert merge sql. That was bad because some adapters specifically don't work with the default macro, and implement their own under the hood. By instead using dbt.get_delete_insert_merge_sql we allow the "normal" macro resolution to occur.

What type of PR is this? (check all applicable)

  • 🍕 Feature
  • 🐛 Bug Fix
  • 📝 Documentation Update
  • 🎨 Style
  • 🧑‍💻 Code Refactor
  • 🔥 Performance Improvements
  • ✅ Test
  • 🤖 Build
  • 🔁 CI
  • 📦 Chore (Release)
  • ⏩ Revert

Related Tickets & Documents

#204

Checklist

  • 💣 Is your change a breaking change?
  • 📖 I have updated the CHANGELOG.md

Added tests?

  • 👍 yes
  • 🙅 no, because they aren't needed
  • 🙋 no, because I need help

Added to documentation?

  • 📓 internal package docs (ymls, macros, readme, if applicable)
  • 📕 I have raised a Snowplow documentation PR if applicable (Link here if required)
  • 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

No

[optional] What gif best describes this PR or how it makes you feel?

timeforpizza

QMalcolm added 2 commits June 26, 2025 17:32
…ge_sql` macro

Previously what was being used was `dbt.default_get_delete_insert_merge_sql`. This
_always_ got the "default" delete insert merge sql. That was bad because some adapters
specifically don't work with the default macro, and implement their own under the
hood. By instead using `dbt.get_delete_insert_merge_sql` we allow the "normal" macro
resolution to occur.
@QMalcolm QMalcolm requested a review from a team as a code owner June 26, 2025 22:46
@snowplowcla snowplowcla added the cla:no [Auto generated] Snowplow Contributor License Agreement has not been signed. label Jun 26, 2025
@snowplowcla
Copy link

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

@QMalcolm
Copy link
Author

I signed it!

@snowplowcla
Copy link

Confirmed! @QMalcolm has signed the Contributor License Agreement. Thanks so much.

@snowplowcla snowplowcla added cla:yes [Auto generated] Snowplow Contributor License Agreement has been signed. and removed cla:no [Auto generated] Snowplow Contributor License Agreement has not been signed. labels Jun 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla:yes [Auto generated] Snowplow Contributor License Agreement has been signed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Alias in delete statement for incremental models persists on dbt cloud

3 participants