⌘K ctrl+k
Search Shortcut cmd + k | ctrl + k
DuckDB 2.0 ドキュメント 全文検索
per page, with , order by , clip by
Results of 1 - 10 of about 46 for server (0.002 sec.)
Reference 12189
This page lists the functions, settings, and log types exposed by the quack extension . For a tour of the protocol, start with the Overview . Function Reference Server Management Function Description quack_serve(⟨listen_uri⟩, ...) Start a server ... n URI, the listen URL, and the authentication token. See the quack_serve parameters below. quack_stop(listen_uri) Stop the server listening on listen_uri . quack_server_list() List the servers running in this instance: listen URI and URL, host, port, n ... mber of active connections, and additional info (IPv6, SSL). quack_active_connections() List the client connections of the servers running in this instance: server, quack_connection_id , last query, state, hashed client id, cached rows, and query start ... time. quack_generate_keys(directory = ⟨path⟩) Generate a self-signed certificate ( server.pem ) and private key ( private_key.pem ) for serving over SSL. Defaults to ~/.duckdb/extension_data/quack ; existing key ...
https://man.mtool.work/duckdb/2.0/quack/reference.html
Quack Remote Protocol 11655
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 ... no custom wire transport to operate. Client-driven request and response. Every interaction is initiated by the client. The server does not initiate interactions via pushing. application/duckdb serialization. Requests and responses are encoded with Duck ... 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 an existing DuckDB session. Everything that the session can see (in- ... les, attached files, schemas) becomes reachable over the remote protocol. To start listening on localhost, run: {:.codebox-server} CALL quack_serve('quack:localhost'); The URI argument is optional: calling quack_serve() without it also listens on quack ...
https://man.mtool.work/duckdb/2.0/quack/overview.html
Security 11564
This page covers Quack's security posture end to end: what the server exposes, what stays local, the role of a TLS-terminating reverse proxy, and the authentication / authorization callbacks the server runs on every connection and every que ... ry. Exposure Model A Quack server exposes the full SQL surface of the underlying DuckDB instance, including read and write access to every table the server' ... s session can see. Because of this, the extension ships with conservative defaults that prevent accidental exposure: The server requires an authentication token , which the client has to supply on every connection. Unless a token is passed explicitly ... or supplied by a quack secret, the server generates a random token at startup. The server binds to localhost only, non-local hostnames require an explicit allow_oth ...
https://man.mtool.work/duckdb/2.0/quack/security.html
Troubleshooting Quack 10740
DuckDB 2.0 ships a polished version of Quack (first released in DuckDB 1.5.3) with substantial performance and stability improvements. If you experience any issues with Quack, try upgrading all your DuckDB clients to the latest version of t ... NSTALL quack; ATTACH Fails to Bind a Remote Table Definition When a Quack client runs ATTACH 'quack:⟨host⟩' , it loads the server's table definitions up front and binds them locally. A single definition that cannot be bound fails the entire attachment, ... even when you only intend to query unrelated, ordinary tables on the server. The attachment does not silently skip the problematic table. A common cause is an Iceberg catalog attached on the server ... N type here is not the table's real type, and it does not mean the client must install the iceberg extension. It means the server has not yet resolved the table's schema. Resolving Tables Eagerly on the Server Attach the Iceberg catalog on the server w ...
https://man.mtool.work/duckdb/2.0/quack/troubleshooting.html
Backup Extension Repositories 10236
The core and community extension repositories have backup servers (see duckdb-backup.org ): Repository Primary server Backup server core http://extensions.duckdb.org http://extensions.duckdb-backup.org community http://community-extensions. ... duckdb.org http://community-extensions.duckdb-backup.org The backup servers serve byte-identical binaries, so signature checks are unaffected. Automatic Fallback Fallback is automatic: if the prima ... ry server is unreachable or returns a 5xx error, INSTALL retries the download from the backup server. No configuration is needed. A ... 4xx error (e.g., a non-existent extension) is reported directly, without contacting the backup server. The fallback only applies to the built-in core and community repositories. Repositories set via custom_extension_reposito ...
https://man.mtool.work/duckdb/2.0/operations_manual/backup_extension_repositorie...
Securing Quack with a Reverse Proxy 10236
By default, the Quack server binds to localhost and speaks plain HTTP. See Security for the rationale behind these configurations. For any deployment beyond local-only, the recommended pattern is the same as for any other HTTP-based databas ... e / application server: put a proven HTTP reverse proxy in front of it, and let the proxy terminate TLS. The Quack client cooperates with this: f ... or non-local URIs it assumes HTTPS by default, so a properly fronted server “just works” from the client side too. This guide walks through three setups, in order of likely usefulness: A local TLS t ... -1 } request_body { max_size 256MB } } Then start Caddy: brew install caddy # macOS, for other platforms see https://caddyserver.com/docs/install caddy run --config Caddyfile The first run will prompt for elevation to install Caddy's local CA into you ...
https://man.mtool.work/duckdb/2.0/quack/setup/reverse_proxy.html
UI Extension 9413
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 ... nment: 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(); You can then load the ... UI in your browser by navigating to http://localhost:4213 . To stop the HTTP server, run: CALL stop_ui_server(); Local Query Execution By default, the DuckDB UI runs your queries fully locally: your queries ... hrough the UI, you have to opt-in explicitly and sign into MotherDuck. Configuration Local Port The local port of the HTTP server can be configured with a SQL command like: SET ui_local_port = 4213; The environment variable ui_local_port can also be us ...
https://man.mtool.work/duckdb/2.0/core_extensions/ui.html
CONNECT and DISCONNECT Statements 9077
New Support for the CONNECT and DISCONNECT statements was introduced in DuckDB 2.0. The CONNECT statement routes the current session to a remote database, so that subsequent queries execute on that remote and their results stream back. DISC ... ONNECT returns the session to the local database. CONNECT is central to using DuckDB as a server : a DuckDB instance can serve its databases over the network, and any other DuckDB can attach to it and route queries ther ... e. Examples Attach a remote DuckDB server over the Quack protocol , route queries to it, and disconnect again: ATTACH 'quack:server.example.com' AS qk (TOKEN '⟨my_t ... oken⟩'); CONNECT qk; SELECT count(*) FROM events; -- executes on the server, results stream back DISCONNECT; Connect directly to a remote database using a connection string. For databases other than ...
https://man.mtool.work/duckdb/2.0/sql/statements/connect.html
Tableau – A Data Visualization Tool 8467
Tableau is a popular commercial data visualization tool. In addition to a large number of built-in connectors, it also provides generic database connectivity via ODBC and JDBC connectors. Tableau has two main versions: Desktop and Online (Server ... working in an embedded environment like Python. For Online, since DuckDB is in-process, the data needs to be either on the server itself or in a remote data bucket that is accessible from the server. Database Creation When using a DuckDB database file ... he JDBC Driver Tableau provides documentation on how to install a JDBC driver for Tableau to use. Both Tableau Desktop and Server need to be restarted any time you add or modify drivers. Driver Links The link here is for a recent version of the JDBC dr ... -provided PostgreSQL dialect. Create a DuckDB file containing your views and/or data. Launch Tableau. Under Connect > To a Server > More…, click on "Other Databases (JDBC)". This brings up the connection dialog box. For the URL, enter jdbc:duckdb:/User ...
https://man.mtool.work/duckdb/2.0/guides/data_viewers/tableau.html
ODBC Extension 8039
Please note that DuckDB also offers an ODBC client , which allows you to connect to DuckDB via ODBC from other applications. The odbc_scanner extension allows connecting to other databases (using their ODBC drivers ) and run queries with th ... atform⟩/odbc_scanner.duckdb_extension.gz'; Support Status of DBMS-Specific Types Tier 1: Oracle: types coverage status SQL Server: types coverage status DB2: types coverage status Tier 2: PostgreSQL: basic types covered MySQL/MariaDB: basic types cover ... t a configured data source: Oracle: Driver={Oracle in instantclient_23_0};DBQ=//127.0.0.1:1521/XE;UID=scott;PWD=tiger; SQL Server: Driver={ODBC Driver 18 for SQL Server};Server=tcp:127.0.0.1,1433;UID=sa;PWD=pwd;TrustServerCertificate=Yes;Database=test_ ... 2 ODBC DRIVER};HostName=127.0.0.1;Port=50000;Database=testdb;UID=db2inst1;PWD=pwd; PostgreSQL: Driver={PostgreSQL Unicode};Server=127.0.0.1;Port=5432;Username=postgres;Password=postgres;Database=test_db; MySQL/MariaDB: Driver={MariaDB ODBC 3.1 Driver}; ...
https://man.mtool.work/duckdb/2.0/core_extensions/odbc/overview.html
PREV 1 2 3 4 5 NEXT
DuckDB 2.0 Documentation / man.mtool.work