Detect execution errors earlier, avoiding the unhelpful "attempting to execute an unsuccessful or closed pending query result" errors#41
Merged
Conversation
Member
Author
|
Opening as draft to reduce tension on CI while releases for v1.4.0 are ongoing |
…tempting to execute and unsuccesful or closed pending query result'
Tishj
force-pushed
the
throw_error_explicitly
branch
from
a8c391f to
24290cf
Compare
Merged
via the queue into
duckdb:v1.4-andium
with commit Sep 11, 2025
bf9b439
65 of 66 checks passed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This PR fixes duckdb/duckdb#18106