-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
The current features and types tables list things without linking to a place that could give the user more information.
For example, "Bulk Ingestion" could be a URL to more info on ADBC bulk ingestion:
And BIGINT and int64 could be links to where those types are documented:
I think a pretty reasonable way to do this would be to,
- For Arrow features and types, encode these in the validation suite codebase itself
- For database-specific stuff, add tags in the validation tests in each driver repo. That way the knowledge about the database stays with the driver.
I think (2) makes sense because we currently store the sql-type-name in the validation suite like this,
json.toml:
[tags]
sql-type-name = "JSON"which could be
[tags]
sql-type-name = "JSON"
sql-type-url = "http://example.com"We could give guidance to driver builders to consider this when building out their tests.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels