Results of 1 - 10 of about 12 for Scheme (0.002 sec.)
- Legacy Authentication Scheme for S3 API 12469
- Prior to version 0.10.0, DuckDB did not have a Secrets manager . Hence, the configuration of and authentication to S3 endpoints was handled via variables. This page documents the legacy authentication scheme for the S3 API. Warning This pag
...oring secrets. The recommended way to configure and authenticate of S3 endpoints is to use secrets . Legacy Authentication Scheme To be able to read or write from S3, the correct region should be set: SET s3_region = 'us-east-1'; Optionally, the endpoi... - https://man.mtool.work/duckdb/2.0/core_extensions/httpfs/s3api_legacy_authentica...
- ATTACH and DETACH Statements 10878
- DuckDB allows attaching to and detaching from database files. Examples Attach the database file.db with the alias inferred from the name ( file ): ATTACH 'file.db'; Attach the database file.db with an explicit alias ( file_db ): ATTACH 'fil
...ded . When TYPE is not specified, DuckDB deduces the type from the path in two steps: If the path begins with a recognized scheme prefix followed by a colon, such as sqlite:file.db , postgres:dbname=postgres , or mysql:db=mysql , the scheme determines...e type to native DuckDB storage and disables the path-based deduction described above. If you attach a path that carries a scheme prefix for another engine but also pass TYPE DUCKDB , the prefix is ignored and the statement does not have the intended e... - https://man.mtool.work/duckdb/2.0/sql/statements/attach.html
- Versioning of Extensions 10082
- Extension Versioning Most software has some sort of version number. Version numbers serve a few important goals: Tie a binary to a specific state of the source code Allow determining the expected feature set Allow determining the state of t
...ure consistent semantics of these version numbers across the various extensions, DuckDB's Core Extensions use a versioning scheme that prescribes how extensions should be versioned. The versioning scheme for Core Extensions is made up of 3 different st... - https://man.mtool.work/duckdb/2.0/extensions/versioning_of_extensions.html
- Quack Remote Protocol 10082
- The Quack extension turns a DuckDB instance into a server that other DuckDB instances (clients) can connect to over HTTP. This page covers the protocol at a glance and walks through basic usage on both sides of the wire. For the full list o
...ks via follow-up FETCH requests, optionally parallelized on multiple threads. Default port: 9494 . All URIs use the quack: scheme, e.g., quack:hostname:port with the port defaulting to 9494 . Server-Side Usage Starting a Server A server is started from...h a TLS-terminating reverse proxy. See Securing Quack with a Reverse Proxy . URI Format Quack endpoints use the quack: URI scheme and 9494 as the default port. Some examples: URI Host Port Comment quack:localhost localhost 9494 quack://localhost localh... - https://man.mtool.work/duckdb/2.0/quack/overview.html
- S3 API Support 9692
- The httpfs extension supports reading/writing/ globbing files on object storage servers using the S3 API. S3 offers a standard API to read and write to remote files (while regular http servers, predating S3, do not offer a common write API)
...quet 2 examplevalue1 s3://bucket-name/file2.parquet Hive Partitioning DuckDB also offers support for the Hive partitioning scheme , which is available when using HTTP(S) and S3 endpoints. Writing Writing to S3 uses the multipart upload API. This allows...r-bucket⟩/partitioned' ( FORMAT parquet, PARTITION_BY (⟨part_col_a⟩, ⟨part_col_b⟩), OVERWRITE_OR_IGNORE true ); The naming scheme of the written files looks like this: s3://⟨your-bucket⟩/partitioned/part_col_a=⟨val⟩/part_col_b=⟨val⟩/data_⟨thread_number... - https://man.mtool.work/duckdb/2.0/core_extensions/httpfs/s3api.html
- S3 and AWS Authentication 9303
- This page is the entry point for authenticating to S3 and other AWS services from DuckDB. Authentication is configured using secrets , and the detailed reference material lives on the S3 API Support and AWS Extension pages. The sections bel
...redentials were loaded through the load_aws_credentials function. This method is deprecated. See the Legacy Authentication Scheme for S3 API page if you are maintaining older setups.... - https://man.mtool.work/duckdb/2.0/core_extensions/httpfs/authentication.html
- Go Client 8101
- The latest stable release of the DuckDB Go client bundles DuckDB 2.0.0. Its own version tag encodes that DuckDB version; see Versioning below. The DuckDB Go client, duckdb-go , is a SQL driver that conforms to Go's built-in database/sql int
...ses. The DuckDB 1.4 Andium LTS release line is published as its own tags, which still follow the client's older versioning scheme. Select one in go.mod the same way as any other version; see the releases page for the available tags. This project moved... - https://man.mtool.work/duckdb/2.0/clients/go/overview.html
- Instantiate 7322
- 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
...sessions, open the database from the browser's Origin Private File System (OPFS) by giving open() a path with the opfs:// scheme: import * as duckdb from '@duckdb/duckdb-wasm'; await db.instantiate(bundle.mainModule, bundle.pthreadWorker); await db.op... - https://man.mtool.work/duckdb/2.0/clients/wasm/instantiation.html
- Release Cycle 7322
- This document outlines the DuckDB and core extension release cycle framework. It is intended for developers working on DuckDB extensions to better understand the underlying processes. Overview DuckDB follows Semantic Versioning ( v<MAJOR>.<
...unstable API extensions into different subcategories. Just like DuckDB itself, these extensions follow the same branching scheme as DuckDB where a combination of main and vx.y-codename play the main role. We will now define the three types of unstable... - https://man.mtool.work/duckdb/2.0/dev/release_cycle.html
- Connect 6915
- Overview Every DuckDB feature reachable from Java starts with a Connection . This page covers the JDBC URL forms the driver accepts, how DuckDB and driver options are passed and which of them win, how connections come to share (or not share
...urns a DuckDB instance into a server that other DuckDB instances can query over HTTP. The JDBC driver has no dedicated URL scheme for it: open a local, usually in-memory, DuckDB connection in the normal way and attach the remote server as a catalog. tr... - https://man.mtool.work/duckdb/2.0/clients/java/connecting.html
DuckDB 2.0 Documentation / man.mtool.work