Reijo Sund

> DuckDB's `UNNEST()` is the equivalent of `tidyr::unchop()`. Our `unnest()` implementation is using it under the hood. Yes, and it is a good practice to use capital letters for native...

Add argument shutdown=TRUE, i.e. use `DBI::dbDisconnect(con, shutdown=TRUE)`

Yes, `defer()` is a good option if `on.exit()` within a function is not enough. For the second question, I agree that it would be nice to have `shutdown=TRUE` as default....

Some more votes for the names pivot_longer and pivot_wider. See [Discord discussion](https://discord.com/channels/909674491309850675/1032659480539824208/1034835594976694282).

Discussed also in #6307

Could you please try to use CRAN-version of DuckDB? I believe that R-universe version includes also `fts` and `json` extensions built in the binary, i.e. should work even without `INSTALL`...

Thanks for testing. Could you please also check that the extension binary is really available in the directory pointed out by the IO Error. If not, you may follow [these...

I'm not quite sure to which part the error is related as it vanishes if any of those three parts (unlist, case when, sum over()) is left out. Maybe something...

`select unnest([ 5, 4, 3 ]) as r, r as x, sum(r) over();` still reproduces the internal error in DuckDB Web Shell [Database: v0.10.1 - Package: @duckdb/[email protected]]

I implemented this one, so a few comments: Object cache related things can be dropped, those are remains from the earlier version that was intended for enabling tbl to work...