Mark Litwintschik

It is, I'm been able to produce the issue ~10 times this morning. I shut down my machine and restarted it as well just incase it was the i9-14900K acting...

```sql D select extension_version from duckdb_extensions() where extension_name = 'spatial'; ┌───────────────────┐ │ extension_version │ │ varchar │ ├───────────────────┤ │ 6826755 │ └───────────────────┘ D force install spatial; D select extension_version from...

It exits without any message each time I run it via cmd.exe and duckdb.exe. ``` C:\Users\markl\Downloads>duckdb.exe v1.0.0 1f98600c2c ``` ```sql D select extension_version from duckdb_extensions() where extension_name = 'spatial'; ┌───────────────────┐...

I have no idea what might have caused this but my Internet connection is very reliable and I'm using it for 10 other things at the moment. I would point...

I'm convinced this is a Windows-specific issue. I'm seeing floating point exceptions with several other datasets I've worked with in other blog posts. When the next stable release of DuckDB...

This issue has now been fixed as of v1.1.1 af39bd0dcf

I'll leave a note here so this issue doesn't go stale. I'll test this dataset against the next DuckDB release when it's made available and report my results here.

I had another go with v1.1.1 af39bd0dcf on Windows 11 running DuckDB via cmd.exe. This time I tried with a single SQL statement. ```bash $ duckdb.exe test.duckdb ``` ```sql INSERT...

The issue has always been that sending a glob of filenames to the CSV parsers made DuckDB behave very differently from how it would behave if handed files one at...