Max Gabrielsson
Max Gabrielsson
Sooo... argh, where to begin? I guess ill just start by responding to some of the points brought up: > What could be very cool, but I don't know if...
> Another approach, that I've had in the back of my mind as one of the long-term goals for DuckDB spatial is to remove GDAL from the spatial extension itself...
I remember seeing a similar issue caused by preprared parameters not getting pushed down into the scan, but will investigate further.
Okay, so I've been digging into this, and the solution is to add two additional conditions `bbox.xmax < 'nan' and bbox.ymax < 'nan';`, to guard against `nan` values in the...
So It seems like I was a bit too quick on the draw. I've been testing out different approaches locally and ended up hitting the recently added [remote file cache](https://github.com/duckdb/duckdb/pull/16463),...
We've now reverted to the previous behavior in regards to NaNs in v1.3.1, so this should be fixed.
This should be fixed since yesterday, could you try reinstalling the v1.2.0 spatial extension? I.e. execute `FORCE INSTALL spatial;` In short, we accidentally introduced a bug in the version of...
@bmcandr Hello! Are you able to provide a reproduction?
Extension version 6b3d93c is not the version that should be distributed for v1.2.1
Alright, seems like we distribute the wrong extension version. This was fixed in a commit after 6b3d93c. Strangely main DuckDB CI is pinned at 919c69fe47443b4eafbd883e2fcac0b2ec448725 and 2905968a85703e5ca3698976daafd759554e1744 on both main...