SQLite extension will not attach the database on a computer without an internet connection

[breckcs]

When using the SQLite extension from a computer without internet access, it fails to attach the database.

The error is: Catalog Error: SET schema: No catalog + schema named "hello" found

The SQLite extension is on the file system, and is installed and used as follows:

INSTALL '/plugins/sqlite_scanner.duckdb_extension';
ATTACH './hello.db' AS hello (TYPE SQLITE, READ_ONLY TRUE); USE 'hello';

This is being called from a Rust application using duckdb-rs.

[breckcs]

We installed an Nginx proxy and served the extensions locally on the computer that doesn't have access to the internet. Now the application works without any code changes. We see the following requests for extensions through the proxy:

GET /v1.1.1/linux_amd64_gcc4/sqlite_scanner.duckdb_extension.gz
GET /v1.1.1/linux_amd64/parquet.duckdb_extension.gz
GET /v1.1.1/linux_amd64/parquet.duckdb_extension.gz
GET /v1.1.1/linux_amd64/sqlite_scanner.duckdb_extension.gz
GET /v1.1.1/linux_amd64/sqlite_scanner.duckdb_extension.gz

[Alex-Monahan]

We installed an Nginx proxy and served the extensions locally on the computer that doesn't have access to the internet. Now the application works without any code changes. We see the following requests for extensions through the proxy:

GET /v1.1.1/linux_amd64_gcc4/sqlite_scanner.duckdb_extension.gz
GET /v1.1.1/linux_amd64/parquet.duckdb_extension.gz
GET /v1.1.1/linux_amd64/parquet.duckdb_extension.gz
GET /v1.1.1/linux_amd64/sqlite_scanner.duckdb_extension.gz
GET /v1.1.1/linux_amd64/sqlite_scanner.duckdb_extension.gz

Hello!

This setting may help! The extensions may be getting autoloaded.
set autoinstall_extension_repository = 'my/path'

[breckcs]

@Alex-Monahan, thank you so much. This resolved our issue.

I created duckdb/duckdb-rs#461 to explore adding the behaviour we want to duckdb-rs.

[breckcs]

We installed an Nginx proxy and served the extensions locally on the computer that doesn't have access to the internet. Now the application works without any code changes. We see the following requests for extensions through the proxy:

GET /v1.1.1/linux_amd64_gcc4/sqlite_scanner.duckdb_extension.gz
GET /v1.1.1/linux_amd64/parquet.duckdb_extension.gz
GET /v1.1.1/linux_amd64/parquet.duckdb_extension.gz
GET /v1.1.1/linux_amd64/sqlite_scanner.duckdb_extension.gz
GET /v1.1.1/linux_amd64/sqlite_scanner.duckdb_extension.gz

Hello!

This setting may help! The extensions may be getting autoloaded. set autoinstall_extension_repository = 'my/path'

Just a note this should be custom_extension_repository, not autoinstall_extension_repository.

The repository can be seeded by copying from the DuckDB extension cache if the extensions have already been installed once:

mv ~/.duckdb/extensions/v1.2.1 my/path