ericemc3

For the record, that other API call crashes DuckDB CLI (current dev 1.3): ``` load spatial ; load httpfs; FROM st_read('/vsicurl/https://geo.api.gouv.fr/communes?codeDepartement=31&geometry=contour&format=geojson'); ``` though ``` load spatial ; FROM st_read('https://geo.api.gouv.fr/communes?codeDepartement=09&geometry=contour&format=geojson'); ```...

Thank you! ``` LOAD spatial ; FROM st_read('https://geo.api.gouv.fr/communes?codePostal=31140&geometry=contour&format=geojson'); ``` works indeed fine now, and without the need of `LOAD HTTPFS;`, which is really great. This works also: ``` LOAD spatial...

This crashes 1.4.2 as well: ``` LOAD spatial ; FROM st_read('https://geo.api.gouv.fr/communes?codeDepartement=91&geometry=contour&format=geojson'); ``` though you can visualize the geojson here: https://gavinr.github.io/geojson-viewer/?url=https%3A%2F%2Fgeo.api.gouv.fr%2Fcommunes%3FcodeDepartement%3D91%26geometry%3Dcontour%26format%3Dgeojson

Thanks, i am on Win11, using the CLI v 1.4.2 ``` LOAD httpfs; LOAD spatial ; FROM st_read('https://geo.api.gouv.fr/communes?codeDepartement=91&geometry=contour&format=geojson'); ``` ClI closes without warning. Same thing with DBeaver (Java DuckDB version)...

FYI: https://github.com/dbeaver/dbeaver/pull/38118

Solved with last early access version (25.1.0) of DBeaver! Looks like they had to adress some changes DuckDB side

Here is an extract from an SVG export with Vectorpea, with inline SVG styles: ``` Oui, tout à fait ``` A better version, more suitable for import in powerpoint for...

Yes indeed, i asked ChatGPT to clean the vectorpea export, and the cleaned version is properly imported in Powerpoint. Here are both files: [pie_export_vectorpea.zip](https://github.com/user-attachments/files/18740176/pie_export_vectorpea.zip) It can also be checked with...

Oh, thank you! Actually, I know the trick, but the lay people I work with don’t — and they won’t remember it ;) DuckDB’s promise is that each file should...

Since the issue is still present in 1.4.2, and to narrow it down, it seems that this performance degradation on Windows originates from the ORDER BY clause — possibly related...