feat(postgresql)!: Update Internal CQ IDs on Upsert #8554
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
erezrokah
approved these changes
Feb 28, 2023
kodiakhq bot
pushed a commit
that referenced
this pull request
Mar 15, 2023
🤖 I have created a release *beep* *boop* --- ## [3.0.0](plugins-destination-postgresql-v2.1.5...plugins-destination-postgresql-v3.0.0) (2023-03-15) ### ⚠ BREAKING CHANGES * **postgresql:** Update Internal CQ IDs on Upsert ([#8554](#8554)) ### Features * **postgresql:** Update Internal CQ IDs on Upsert ([#8554](#8554)) ([e820b01](e820b01)) ### Bug Fixes * **deps:** Update module github.com/cloudquery/plugin-sdk to v1.43.0 ([#8949](#8949)) ([31dfc63](31dfc63)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
Prior to this change
_cq_idand_parent_cq_idwere never updated on an upsert. Now if CQ tries to do an upsert the ids will also update ensuring that there is always a connection between a parent and relation_cq_id