With the duckdb package version 1.1.3, on Ubuntu 24.10 I see:
library(duckdb)
#> Loading required package: DBI
con <- dbConnect(duckdb())
dbExecute(con, "INSTALL spatial;")
#> Error in `duckdb_result()`:
#> ! rapi_execute: Failed to run query
#> Error: IO Error: Failed to install 'spatial'
#> The file was built for DuckDB version 'v1.1.3', but we can only load extensions built for DuckDB version '19864453f7'.
dbGetQuery(con, "PRAGMA version;")
#> library_version source_id
#> 1 v1.1.3-dev165 19864453f7
Created on 2024-12-03 with reprex v2.1.1
This doesn't happen with the duckdb cli:
duckdb
v1.1.3 19864453f7
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
D pragma version;
┌─────────────────┬────────────┐
│ library_version │ source_id │
│ varchar │ varchar │
├─────────────────┼────────────┤
│ v1.1.3 │ 19864453f7 │
└─────────────────┴────────────┘
With the R package, it seems like the extension installer is picking up the source_id instead of the version number. I am just guessing, but I'm wondering if it's because the duckdb version bundled with the R package has the dev165 suffix?
With the duckdb package version 1.1.3, on Ubuntu 24.10 I see:
Created on 2024-12-03 with reprex v2.1.1
This doesn't happen with the duckdb cli:
With the R package, it seems like the extension installer is picking up the
source_idinstead of the version number. I am just guessing, but I'm wondering if it's because the duckdb version bundled with the R package has thedev165suffix?