Closed bouvierr closed 4 months ago
It's implemented in the Reader Type Overhaul and will be released after DuckDB 0.10 is released.
Glad to hear this will be fixed in the next release!
I tried out Reader Type Overhaul.
In TimestampTests.QueryScalarTest
, if I replace TIMESTAMP
by TIMESTAMP_NS
in the Command.CommandText
, the test fails because we get a DuckDBTimestamp
instead of a DateTime
. I was wondering if this is the expected behavior? The Date and Time values are all good though.
Thanks.
I made some changes to the returned types in that branch. I will check the behaviour you described.
@bouvierr Can you clarify which test you mean?
It should be fixed now.
Awesome. Thanks!
This is now merged into develop and will be included in the next release.
I am using DuckDB.NET.Data.Full 0.9.2.
When I call
DuckDB.NET.Data.DuckDBDataReader.GetSchemaTable
, I get the following exception if any column is of typeTIMESTAMP_NS
:If I change the type to its alias with
ALTER TABLE mytable ALTER TargetDate TYPE TIMESTAMP
, thenGetSchemaTable
works fine.I believe the issue is simply that the code currently supports only the type alias
TIMESTAMP
and not the official typeTIMESTAMP_NS
.