Results of 1 - 10 of about 16 for Port (0.002 sec.)
- MySQL Extension 11246
- The mysql extension allows DuckDB to directly read and write data from/to a running MySQL instance. The data can be queried directly from the underlying MySQL database. Data can be loaded from MySQL tables into DuckDB tables, or vice versa.
...ase accessible to DuckDB use the ATTACH command with the mysql or the mysql_scanner type: ATTACH 'host=localhost user=root port=0 database=mysql' AS mysqldb (TYPE mysql); USE mysqldb; Warning Avoid including credentials, such as a password, directly...t variable. Setting Default Environment variable database NULL MYSQL_DATABASE host localhost MYSQL_HOST password MYSQL_PWD port 0 MYSQL_TCP_PORT socket NULL MYSQL_UNIX_PORT user current user MYSQL_USER ssl_mode preferred ssl_ca ssl_capath ssl_cert ss...pecified with secrets . The following syntax can be used to create a secret. CREATE SECRET ( TYPE mysql, HOST '127.0.0.1', PORT 0, DATABASE mysql, USER 'mysql', PASSWORD '' ); The information from the secret will be used when ATTACH is called. We can... - https://man.mtool.work/duckdb/2.0/core_extensions/mysql.html
- PostgreSQL Extension and the Secret Manager 11246
- User credentials and other PostgreSQL database connection details can be stored using the DuckDB Secrets Manager . The following syntax can be used to create a secret: CREATE SECRET ( TYPE postgres, HOST '127.0.0.1', PORT 5432, DATABASE pos
...instances. Secrets can be given a name upon creation. CREATE SECRET postgres_secret_one ( TYPE postgres, HOST '127.0.0.1', PORT 5432, DATABASE postgres, USER 'postgres', PASSWORD '' ); The secret can then be explicitly referenced using the SECRET par...better security, store credentials using DuckDB-managed secrets. Secret Configuration Options Secrets of type postgres support a number of configuration options. The following options are named after the corresponding connection options of libpq : H...OST HOSTADDR PORT DBNAME USER PASSWORD PASSFILE REQUIRE_AUTH CHANNEL_BINDING CONNECT_TIMEOUT CLIENT_ENCODING OPTIONS APPLICATION_NAME FALLBA... - https://man.mtool.work/duckdb/2.0/core_extensions/postgres/secrets.html
- UI Extension 11107
- 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
...u would like to use MotherDuck through 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 var...iable ui_local_port can also be used. The default port is 4213. (Why? 4 = D, 21 = U, 3 = C) Remote URL The local HTTP server fetches the files...s as storage internally (e.g., for saving notebooks). Therefore, running the UI directly on a read-only database is not supported : duckdb -ui -readonly read_only_test.db In the UI, this results in: Catalog Error: SET schema: No catalog + schema name... - https://man.mtool.work/duckdb/2.0/core_extensions/ui.html
- PostgreSQL Import 10379
- To run a query directly on a running PostgreSQL database, the postgres extension is required. Installation and Loading The extension can be installed using the INSTALL SQL command. This only needs to be run once. INSTALL postgres; To load t
...of valid arguments. Name Description Default host Name of host to connect to localhost hostaddr Host IP address localhost port Port number 5432 user PostgreSQL user name [OS user name] password PostgreSQL password dbname Database name [user] passfil...sswords are stored in ~/.pgpass -- Attach the PostgreSQL database using the given connection string ATTACH 'host=localhost port=5432 dbname=mydb' AS test (TYPE postgres); -- The table "tbl_name" can now be queried as if it is a regular table SELECT *... - https://man.mtool.work/duckdb/2.0/guides/database_integration/postgres.html
- ODBC Extension 9634
- 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
...nightly-extensions.duckdb.org/odbc_scanner/⟨7_character_commit_id⟩/v1.2.0/⟨platform⟩/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....0.1,1433;UID=sa;PWD=pwd;TrustServerCertificate=Yes;Database=test_db; DB2: Driver={IBM DB2 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=po...stgres;Password=postgres;Database=test_db; MySQL/MariaDB: Driver={MariaDB ODBC 3.1 Driver};SERVER=127.0.0.1;PORT=3306;USER=root;PASSWORD=root;DATABASE=test_db; Firebird: Driver={Firebird ODBC Driver};Database=127.0.0.1/3050:C:/path/to/... - https://man.mtool.work/duckdb/2.0/core_extensions/odbc/overview.html
- Securing Quack with a Reverse Proxy 9201
- 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
...the certificate with certbot --nginx -d quack.example.com . Clients connect over HTTPS automatically. As the default Quack port remains 9494 even with HTTPS, specify the proxy's port 443 explicitly: {:.codebox-client} ATTACH 'quack:quack.example.com:...t): {:.codebox-server} CALL quack_serve('quack:localhost'); Clients connect over HTTPS automatically. As the default Quack port remains 9494 even with HTTPS, specify the proxy's port 443 explicitly: {:.codebox-client} ATTACH 'quack:quack.example.com:... - https://man.mtool.work/duckdb/2.0/quack/setup/reverse_proxy.html
- Quack Remote Protocol 9062
- 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
...ls, and reverse proxies handle Quack traffic the same way they handle any other HTTP service. There is no custom wire transport to operate. Client-driven request and response. Every interaction is initiated by the client. The server does not initiate...ir. Large results stream back in chunks 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 Sta...xy. 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 localhost 9494 quack:myhost:9000 my... - https://man.mtool.work/duckdb/2.0/quack/overview.html
- Quack on WebAssembly 9062
- CloudFormation Stack We provide an example template for initializing a CloudFormation stack, based on pre-baked public AMI, based on Ubuntu, which will: via DuckDB, install and load Quack, create a randomized token, and do quack_serve on th
...e 0.0.0.0:1294 port. setup via nginx a proxy between 0.0.0.0:1294 and the incoming :443 port obtain a valid TLS certificate via Let's Encrypt...All together, this allows to expose the local 0.0.0.0:1294 port to the public EC2 instance IP via HTTPS. The template is reachable at https://duckdb-quack-ami.s3.us-east-1.amazonaws.com/... - https://man.mtool.work/duckdb/2.0/quack/setup/quack_wasm.html
- MySQL Import 8768
- To run a query directly on a running MySQL database, the mysql extension is required. Installation and Loading The extension can be installed using the INSTALL SQL command. This only needs to be run once. INSTALL mysql; To load the mysql ex
...l extension is installed, you can attach to a MySQL database using the following command: ATTACH 'host=localhost user=root port=0 database=mysqlscanner' AS mysql_db (TYPE mysql); USE mysql_db; The string used by ATTACH is a PostgreSQL-style connectio...ents. Any options not provided are replaced by their default values. Setting Default database NULL host localhost password port 0 socket NULL user current user You can directly read and write the MySQL database: CREATE TABLE tbl (id INTEGER, name VAR...CHAR); INSERT INTO tbl VALUES (42, 'DuckDB'); For a list of supported operations, see the MySQL extension documentation . To run entire queries on the MySQL server instead of scanning its ta... - https://man.mtool.work/duckdb/2.0/guides/database_integration/mysql.html
- Amazon RDS with IAM Authentication 8335
- Managed PostgreSQL databases on Amazon RDS and Aurora can authenticate with short-lived IAM tokens instead of a static password. DuckDB supports this through the postgres and aws extensions: the aws extension generates the token from an AWS
...'env;sso', REGION '⟨eu-west-1⟩', RDS_USER '⟨postgres⟩', RDS_HOST '⟨instance⟩.⟨identifier⟩.⟨region⟩.rds.amazonaws.com', RDS_PORT '5432' ); Then create a secret of type postgres that references it via AWS_RDS_SECRET . Because no password is set, the to...ed) automatically: CREATE SECRET pg_rds_secret ( TYPE postgres, HOST '⟨instance⟩.⟨identifier⟩.⟨region⟩.rds.amazonaws.com', PORT '5432', USER '⟨postgres⟩', DATABASE '⟨postgres⟩', SSLMODE require, AWS_RDS_SECRET aws_rds_secret ); Connecting and Queryin... - https://man.mtool.work/duckdb/2.0/guides/database_integration/rds_iam.html
DuckDB 2.0 Documentation / man.mtool.work