Support additional DuckDB integer types such as HUGEINT, UHUGEINT, etc #1797
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.
Adds
DataType
support for the following integer types, with tests:HUGEINT
(128bit)UHUGEINT
(128bit, unsigned)UTINYINT
USMALLINT
UBIGINT
(ref: https://duckdb.org/docs/stable/sql/data_types/numeric.html#integer-types)
Also: standardised link text/case for database names. Was mixed between (for example)
[Postgres]
,[postgres]
,[postgresql]
, etc. That is now standardised to[PostgreSQL]
, and other DB names were similarly case-standardised (bigquery → BigQuery
,clickhouse → ClickHouse
, etc).Cleaned up a few other minor nits in the DataType docstrings.
Note: the
clippy
lint from the new Rust version is addressed by #1796; I can rebase on that once it is merged.