Skip to content

Conversation

Tishj
Copy link
Contributor

@Tishj Tishj commented Jan 27, 2025

This PR fixes https://github.com/duckdblabs/duckdb-internal/issues/3670

Finalize the local append before attempting an update, or the node we're looking for is not reachable yet

@Tishj Tishj requested a review from taniabogatsch January 27, 2025 10:03
@duckdb-draftbot duckdb-draftbot marked this pull request as draft January 28, 2025 11:18
@Tishj Tishj marked this pull request as ready for review January 28, 2025 11:20
@Mytherin
Copy link
Collaborator

Thanks! Could you just resolve the merge conflicts?

@duckdb-draftbot duckdb-draftbot marked this pull request as draft February 3, 2025 08:44
@Tishj Tishj marked this pull request as ready for review February 3, 2025 08:45
@Tishj
Copy link
Contributor Author

Tishj commented Feb 4, 2025

@Mytherin could you review this?
I think it's good to go

@Mytherin Mytherin changed the base branch from main to v1.2-histrionicus February 4, 2025 13:37
@Mytherin Mytherin merged commit 22158bb into duckdb:v1.2-histrionicus Feb 4, 2025
50 checks passed
@Mytherin
Copy link
Collaborator

Mytherin commented Feb 4, 2025

Thanks!

Mytherin added a commit that referenced this pull request Feb 4, 2025
… DO ...) (#15977)

This PR fixes #15791

This branch is made from <#15927>
as both of them touch the same code and needed partially the same
changes.

The RETURNING result is now properly made to include each insert/update
that gets made, instead of the optimistic approach that was taken
before.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants