[DBAPI2.0] Fix the description attribute
#43
Merged
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.
Fixes https://github.com/duckdblabs/duckdb-internal/issues/1217, duckdb/duckdb#10495
This PR should make a better attempt at implementing https://peps.python.org/pep-0249/#type-objects-and-constructors
We add the required type object sentinels:
STRINGNUMBERDATETIMEBINARYROWID(None, as DuckDB doesn't have a way to detect this on a LogicalType)The objects returned for the
type_codeof thedescriptionis aDuckDBPyType.The sentinels are of type
DBAPITypeObjectand are overloaded to be compared with theDuckDBPyTypeobjects.The constructors listed by the PEP are not added, they could be added in the future.