Admolly

I'd like to add my 2 cents to this discussion because we use DuckDB in production and faced this issue. @kuatroka It's not really clear to me what exactly Option...

Experiencing the same problem as ppfreitas. Having another workaround/fix would be nice!

I'm working on it. Since the data is proprietary and I don't completely understand the bug I'm having a hard time doing that.

I think something may have gone wrong during the EXPORT/IMPORT step, as I'm also encountering some issues with timestamp columns. Are there any options I can specify when copying tables...

For instance, I found the following from this query, the date and date parts don't match up: ``` select id, database, birthdate::date birthdate, extract(day from birthdate), extract(month from birthdate), extract(year...

Another annoying thing: if I downgrade back to 0.4.0, duckdb can open the database file of the old version of the DB, but cannot read any of the tables. In...

OK, so apparently duckdb throws an error if you query a timestamp prior to 1677-09-22. If you try to coerce that timestamp to a date, it will tell you that...

Some more details: - I tried the query in the CLI and still it throws the same error: `Error: near line 2: Invalid Error: String value is not valid UTF8`....

Hi Hannes, thank you for your response. I am indeed working on creating a reproducible example, but please bare in mind that, without a better understanding of the bug, this...

Hi @hannes I have an anonymized dataset ready that illustrates the bug. Can you suggest a secure way for us to transfer you the files?