Today I'll be upgrading a couple of things to #DuckDB 1.5 and yet again, the folks at @duckdb provide a perfect way to adapt to a breaking change, here getting the order of x/y right:

- in 1.5 you can set geometry_always_xy = true to have xy in lat/long order, otherwise you get a warning
- in 2.0 not setting it, you get an error, but you can ofc use false to get <= 1.5 default behaviour
- in 2.1 make the new one the default

They did the same in 1.3 for lambda style.

https://duckdb.org/2026/03/09/announcing-duckdb-150#spatial-extension