You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been looking at how parameterized types are represented in the schema returned by AdbcConnectionGetObjects. I found that for DECIMAL(precision, scale), the precision and scale map to xdbc_column_size and xdbc_decimal_digits respectively. However, I wasn't able to determine where the time unit (s/ms/us/ns) of a TIMESTAMP type should be specified.
From my understanding, the column properties in COLUMN_SCHEMA are designed to mirror JDBC/ODBC metadata. However, I haven't found any standardized documentation that explicitly states how timestamp precision should be represented in this context.
My questions:
Is there a standard way to represent timestamp precision in the ADBC metadata schema?
If so, which field should hold this information?
Does this align with JDBC/ODBC metadata standards, and if so, where is it documented?
Any clarification on this would be greatly appreciated! Thanks in advance.
The text was updated successfully, but these errors were encountered:
You can use GetTableSchema to get the Arrow schema directly, otherwise I don't think any driver currently populates any field for timestamp precision. IIRC, for JDBC/ODBC it ends up as the decimal precision or column size and we should be consistent with that when implemented.
I have been looking at how parameterized types are represented in the schema returned by
AdbcConnectionGetObjects
. I found that forDECIMAL(precision, scale)
, the precision and scale map toxdbc_column_size
andxdbc_decimal_digits
respectively. However, I wasn't able to determine where the time unit (s
/ms
/us
/ns
) of aTIMESTAMP
type should be specified.From my understanding, the column properties in
COLUMN_SCHEMA
are designed to mirror JDBC/ODBC metadata. However, I haven't found any standardized documentation that explicitly states how timestamp precision should be represented in this context.My questions:
Any clarification on this would be greatly appreciated! Thanks in advance.
The text was updated successfully, but these errors were encountered: