duckdb_columns() produces NULL value as DATA_TYPE for certain INFORMATION_SCHEMA columns #11281
Closed
Description
What happens?
When using duckdb_columns() to introspect the INFORMATION_SCHEMA, certain columns don't list the correct DATA_TYPE
To Reproduce
select table_name, column_name
from duckdb_columns()
where database_name = 'system'
and schema_name = 'information_schema'
and data_type = 'NULL'This produces:
|table_name |column_name |
|--------------|-----------------------------|
|character_sets|character_set_catalog |
|character_sets|character_set_schema |
|columns |character_octet_length |
|columns |datetime_precision |
|columns |interval_type |
|columns |interval_precision |
|columns |character_set_catalog |
|columns |character_set_schema |
|columns |character_set_name |
|columns |collation_catalog |
|columns |collation_schema |
|columns |collation_name |
|columns |domain_catalog |
|columns |domain_schema |
|columns |domain_name |
|columns |udt_catalog |
|columns |udt_schema |
|columns |udt_name |
|columns |scope_catalog |
|columns |scope_schema |
|columns |scope_name |
|columns |maximum_cardinality |
|columns |dtd_identifier |
|columns |is_self_referencing |
|columns |is_identity |
|columns |identity_generation |
|columns |identity_start |
|columns |identity_increment |
|columns |identity_maximum |
|columns |identity_minimum |
|columns |identity_cycle |
|columns |is_generated |
|columns |generation_expression |
|columns |is_updatable |
|schemata |default_character_set_catalog|
|schemata |default_character_set_schema |
|schemata |default_character_set_name |
|tables |self_referencing_column_name |
|tables |reference_generation |
|tables |user_defined_type_catalog |
|tables |user_defined_type_schema |
|tables |user_defined_type_name |
Note, I couldn't test the latest snapshots because of:
OS:
Microsoft Windows [Version 10.0.22631.3296]
DuckDB Version:
0.10.0
DuckDB Client:
JDBC
Full Name:
Lukas Eder
Affiliation:
Data Geekery
Have you tried this on the latest nightly build?
I have tested with a release build (and could not test with a nightly build)
Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
- Yes, I have