Results of 1 - 10 of about 14 for served (0.001 sec.)
- Deploy 14546
- Overview Deploying DuckDB-Wasm means serving its components so that the browser can fetch and instantiate them. This page describes each component a deployment needs to serve, how the worker and WebAssembly variants relate, how extensions a
...re served and mirrored, and the security considerations involved. A DuckDB-Wasm deployment needs to access the following components:...ipt in the npm @duckdb/duckdb-wasm package. You can deploy it in one of three ways: Bundled together with your application Served from a same-origin (sub-)domain and included at runtime Served from a third-party CDN such as jsDelivr It cannot be served...S Worker Component This is distributed as a JavaScript file in three different flavors, mvp , eh and coi , and needs to be served as-is. The main library component needs to be informed of the actual location. The three variants target three different W... - https://man.mtool.work/duckdb/2.0/clients/wasm/deploying_duckdb_wasm.html
- Load Extensions 9995
- Overview DuckDB-Wasm's (dynamic) extension loading is modeled after regular DuckDB's extension loading, with a few relevant differences due to the difference in platform. A growing subset of core, community, and external extensions is suppo
...mat, how INSTALL and LOAD behave, autoloading, which extensions are available, signing, and how extensions are fetched and served. Format Extensions in DuckDB are binaries to be dynamically loaded via dlopen . A cryptographical signature is appended to...still keep a valid signature (e.g., for local development). Fetching DuckDB-Wasm Extensions Official DuckDB extensions are served at extensions.duckdb.org , which is used as the extension repository unless custom_extension_repository is set. When insta...atform/$name.duckdb_extension.wasm . Note that an additional duckdb-wasm is added to the folder structure, and the file is served as a .wasm file. DuckDB-Wasm extensions are served pre-compressed using Brotli compression. While fetched from a browser,... - https://man.mtool.work/duckdb/2.0/clients/wasm/extensions.html
- Troubleshoot 9662
- Overview This page collects common issues encountered when using DuckDB-Wasm, together with their workarounds. If you run into a problem that is not covered here, search the duckdb-wasm issue tracker on GitHub. Network Error When Querying R
...ser to allow the connection, exactly as for remote data files above. Extensions remain signed regardless of where they are served, so copying an extension to a different location keeps its signature valid. Out of Memory The WebAssembly client has a lim...SharedArrayBuffer , which browsers only expose to pages that are cross-origin isolated . If the top-level document is not served with the Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy headers, DuckDB-Wasm falls back to the single-threade...d reading remote files that are subject to the CORS rules above. Load Extensions — how extensions are fetched, signed, and served, including the httpfs CORS behavior. Deploy — serving components and configuring cross-origin isolation for threading.... - https://man.mtool.work/duckdb/2.0/clients/wasm/troubleshoot.html
- DuckDB Repositories 8559
- Several components of DuckDB are maintained in separate repositories. Main Repositories duckdb : core DuckDB project duckdb-web : documentation and blog duckdb-quack : Quack remote protocol Clients duckdb-go : Go client duckdb-java : Java (
...kdb-ui : web UI for DuckDB Core extension repositories are linked in the Official Extensions page Community extensions are served from the Community Extensions repository Specifications DuckLake specification... - https://man.mtool.work/duckdb/2.0/dev/repositories.html
- Instantiate 8454
- Overview DuckDB-Wasm can be instantiated in several ways, depending on how your application bundles and serves its assets. Each approach resolves the mainModule (the WebAssembly file) and the mainWorker (the worker script) for the browser's
...pabilities, then hands them to AsyncDuckDB . This page shows the patterns for a jsDelivr CDN, webpack, Vite and statically served files. Once instantiated, the db object is used to import data and run queries . Bundle Selection DuckDB-Wasm ships severa...nst db = new duckdb.AsyncDuckDB(logger, worker); await db.instantiate(bundle.mainModule, bundle.pthreadWorker); Statically Served If you would rather not depend on a CDN or a bundler, you can host the DuckDB-Wasm files yourself. Manually download the d...readed, and bundle.pthreadWorker is null . Two things to keep in mind when deploying the threaded bundle: The page must be served with the Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp headers, which is what mak... - https://man.mtool.work/duckdb/2.0/clients/wasm/instantiation.html
- Tigris Import 8332
- Prerequisites For Tigris , the S3-compatible API allows you to use DuckDB's S3 support to read and write from Tigris buckets. This requires the httpfs extension , which can be installed using the INSTALL SQL command. This only needs to be r
...E s3 . Tip When DuckDB runs on a Fly.io Machine, requests to fly.storage.tigris.dev stay on Fly's internal network and are served from the same region as the Machine when possible. Querying After setting up the Tigris credentials, you can query the dat... - https://man.mtool.work/duckdb/2.0/guides/network_cloud_storage/tigris_import.htm...
- Extension Repositories 8122
- New Support for custom extension repositories was introduced in DuckDB 2.0. This feature is currently work-in-progress and the syntax may still change. By default, DuckDB installs extensions from its built-in repositories ( core , core_nigh
...ilt-in ones. A repository is a name, a URL prefix, and one or more RSA public keys that are trusted to sign the extensions served from it. Enabling Custom Repositories Adding custom repositories is gated by the allow_extension_repositories setting. It... - https://man.mtool.work/duckdb/2.0/extensions/extension_repositories.html
- Troubleshooting of Extensions 7999
- You might be visiting this page directed via a DuckDB error message, similar to: INSTALL non_existing; HTTP Error: Failed to download extension "non_existing" at URL "http://extensions.duckdb.org/v2.0.0/osx_arm64/non_existing.duckdb_extensi
...n HTTP 451 (“Unavailable For Legal Reasons”) error when installing an extension means that the extension repository is not served to your location: HTTP Error: Failed to download extension "..." at URL "https://extensions.duckdb.org/..." (HTTP 451) The... - https://man.mtool.work/duckdb/2.0/extensions/troubleshooting.html
- UI Extension 7894
- The ui extension adds a user interface for your local DuckDB instance. Usage To start the UI from the command line: duckdb -ui To start the UI from SQL: CALL start_ui(); Running either of these will open the UI in your default browser. The
...of your local environment: all cores, memory and files. Closing this instance will cause the UI to stop working. The UI is served from an HTTP server embedded in DuckDB. To start this server without launching the browser, run: CALL start_ui_server(); Y... - https://man.mtool.work/duckdb/2.0/core_extensions/ui.html
- Command Line Arguments 7789
- The table below summarizes DuckDB's command line options. To list all command line options, use the command: duckdb -help For a list of dot commands available in the CLI shell, see the Dot Commands page . Argument Description -agent Render
...Both arguments accept a connection type and an optional named secret in the form TYPE:SECRET . Only the quack type can be served. For example, after creating a persistent Quack secret named analytics , serve or connect with: duckdb analytics.duckdb -s... - https://man.mtool.work/duckdb/2.0/clients/cli/arguments.html
DuckDB 2.0 Documentation / man.mtool.work