DuckDB extension commands

reference

TL;DR

Look up authentication, catalog discovery and attachment forms for the BoilStream extension. Use the native DuckDB build matched to your server release. Catalog discovery does not attach a catalog, and attachment uses a UUID rather than its display name. Credentials belong in an authorized session, not saved example scripts.

Message sequenceDiscover an authorized catalog before attaching it

Discovery does not attach a database. The native managed path and browser DuckDB-WASM have different capabilities.

Jump to reference ↓

Catalog functions

Form	Purpose
`PRAGMA boilstream_bootstrap_session(url)`	Authenticate with a bootstrap token
`PRAGMA boilstream_register_user(url, password)`	Begin account registration
`PRAGMA boilstream_verify_mfa(totp_code)`	Complete MFA registration
`PRAGMA boilstream_login(url, password, mfa)`	Interactive login
`FROM boilstream_ducklakes()`	List authorized catalogs and their UUIDs
`FROM boilstream_secrets()`	List cached non-catalog secrets
`PRAGMA boilstream_create_ducklake(name, description)`	Create a catalog; it still needs explicit attachment
`PRAGMA boilstream_attach_ducklake(id, alias)`	Attach by UUID under a local alias
`PRAGMA boilstream_help`	Show extension help

Sharing grants access to the owner’s catalog without copying its data. See Multi-tenancy and catalog sharing for access modes and revocation.