Repository navigation
release duckdb-sqlalchemy 1.5.6.11 - #233
Merged
Merged
Conversation
Name the sequence behind an autoincrement primary key with duckdb_sequence_name, stop raw DBAPI cursor calls from cutting short an open result, and handle abandoned results on DuckDB 2.0.
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
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
Releases 1.5.6.11.
duckdb_sequence_name(Let a column name its implicit sequence withduckdb_sequence_name#229): aColumnoption that names the sequence behind an autoincrement integer primary key, so a model shared with PostgreSQL keeps one sequence name on both databases.connection.connection.cursor().register(...)buffers a SQLAlchemy result that is still being read. On DuckDB 1.x that result silently lost every row after its current 2048-row vector.register(), largeexecutemanyINSERTs,insert_from_arrowand raw driver calls, which DuckDB 2.0 otherwise refuses. Theduckdb<2requirement is unchanged.noxmatrix, and a benchmark summary.pyproject.tomlanduv.lock, withCHANGELOG.mdanddocs/breaking-changes.mdentries.Test evidence
Full suite on this branch:
twine check. The wheel passesscripts/verify_distribution.pyin a fresh Python 3.13 environment with pyarrow and pandas.noxmatrix and the MotherDuck examples.