New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python DBAPI 2.0 Compatibility #1967
Comments
This is related to #469 as well |
@Mause Yeah, I noticed this when I started trying to port the SQLite tests. I think there are two things in play, there's compatibility with the DB-API and compatibility with SQLite (which isn't completely conformant, and implements some of the extensions as well). I had a go at trying to build a pure Python wrapper which was more conformant, but I've unfortunately been waylaid with other things: https://github.com/thesketh/pyduckdb |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stale for 30 days with no activity. |
I figured it might be worth documenting some of the gaps that I've found while trying to build out the sqlalchemy driver for duckdb
The specification is available here: https://peps.python.org/pep-0249/
description
throws an exception instead of returning None when no result set is open (fixed in Return None from description property if there is no open result set #1963)description
is missing mandatorytype_code
value (Add type_code python field #1990)fetchmany
method on cursorlastrowid
(raised in sql insert: access last inserted id #3976)The text was updated successfully, but these errors were encountered: