Impossible to connect to motherduck db

[Upipa]

At the moment, it seems impossible for Windows user to connect to motherduck db through the duckdb package and consequently with ragnar too. The problem seems about the way is compiled the duckdb version shipped with the duckdb package. This problem cause the installation of the motherduck extension to fail. Do you have some workaround to suggest?

[t-kalinowski]

This is surprising. I can investegate next time I'm on windows.

My first guess is that this is likely due to a package upgrade issue. Can you confirm you're running the latest versions of duckdb, DBI, and related packages?

[dfalbel]

It may be something like: #70 (comment).
There's also: #141

It would be helpful to see the error message you get when trying to initialize the MotherDuck extension @Upipa

[Upipa]

store <- ragnar_store_create(
+   store_location,
+   \(x) embed_azure_openai(x, model = "text-embedding-3-small")
+ )

Error in duckdb_result():
! Invalid Error: HTTP Error: Failed to download extension "motherduck" at URL "http://extensions.duckdb.org/v1.5.2/windows_amd64_mingw/motherduck.duckdb_extension.gz" (HTTP 404)
Extension "motherduck" is an existing extension.

For more info, visit https://duckdb.org/docs/stable/extensions/troubleshooting?version=v1.5.2&platform=windows_amd64_mingw&extension=motherduck
ℹ Context: rapi_execute
ℹ Error type: INVALID

This is the error. The error it's pretty straightforward, the link http://extensions.duckdb.org/v1.5.2/windows_amd64_mingw/motherduck.duckdb_extension.gz doesn't exist. It exists http://extensions.duckdb.org/v1.5.2/windows_amd64/motherduck.duckdb_extension.gz. I don't know the exact tecnicality, but as far as i understood, the way is compiled the binary of duckdb shipped with the package maps to a link for the motherduck extension that doesn't exists, because the extension isn't compiled in the same way. I don't know exactly, but the link is constructed from the platform variable of duckdb, and the platform variable of duckdb is amd64_mingw instead of simply amd64. This problem is ralated to different issues in duckdb in which other extensions has the same problem.

duckdb/duckdb-r#2234
duckdb/duckdb-r#1581

maybe even this is related
duckdb/duckdb-r#100

[Upipa]

I forgot to say that i've updated all my packages before doing this test, just to be sure that wasn't a version problem

[dfalbel]

R is compiled with the MinGW compiler while most C++ code nowadays is compiled with the visual studio compiler. Those compilers are not compatible in a way that shared objects compiled with vsc can't be used together with objects compiled with mingw.

So for this to work, we would need MotherDuck to provide a build of the extension compiled with mingw - which I assume is what the _mingw means and is not currently available.

Since extensions versions are tied to ducked package versions, we may be able to find a duck db package version for which the mingw version of MotherDuck is built with mingw and can be used with R.

[Upipa]

Sorry, is there any news on this? Is there a workaround for this problem?