Results of 1 - 10 of about 71 for back (0.001 sec.)
- Editing 12973
- The linenoise-based CLI editor is available for macOS, Linux and Windows. DuckDB's CLI uses a line-editing library based on linenoise , which has shortcuts that are based on Emacs mode of readline . Below is a list of available commands. Yo
...u can also view these shortcuts from within the CLI using .help shortcuts . Moving Key Action Left Move back a character Right Move forward a character Up Move up a line. When on the first line, move to previous history entry Down...When on last line, move to next history entry Home Move to beginning of buffer End Move to end of buffer Ctrl + Left Move back a word Ctrl + Right Move forward a word Ctrl + A Move to beginning of line Ctrl + B Move back a character Ctrl + E Move to...end of line Ctrl + F Move forward a character Alt + Left Move back a word Alt + Right Move forward a word History Key Action Ctrl + P Move to previous history entry Ctrl + N Move to next hi... - https://man.mtool.work/duckdb/2.0/clients/cli/editing.html
- Transaction Management 12299
- DuckDB supports ACID database transactions . Transactions provide isolation, i.e., changes made by a transaction are not visible from concurrent transactions until it is committed. A transaction can also be aborted, which discards any chang
...e). To commit a transaction, run: COMMIT; If you are not in an active transaction, the COMMIT statement will fail. Rolling Back a Transaction You can abort a transaction. This operation, also known as rolling back, will discard any changes the transa...ction made to the database. To abort a transaction, run: ROLLBACK; You can also use the abort command, which has an identical behavior: ABORT; If you are not in an active transaction, the...ROLLBACK and ABORT statements will fail. Multi-Statement Transactions When multiple SQL statements are submitted together (e.g., se... - https://man.mtool.work/duckdb/2.0/sql/statements/transactions.html
- JSON Type 9825
- DuckDB supports json via the JSON logical type. For example: SELECT '[1, null, {"key": "value"}]'::JSON; [1, null, {"key": "value"}] Logically, the JSON type is similar to a VARCHAR , but with the restriction that it must be valid JSON. Phy
...bjects: SELECT '{"a":1,"a":2}'::JSON; {"a":1,"a":2} We allow any of DuckDB's types to be cast to JSON, and JSON to be cast back to any of DuckDB's types, for example, to cast JSON to DuckDB's STRUCT type, run: SELECT '{"duck": 42}'::JSON::STRUCT(duck...INTEGER); {'duck': 42} And back: SELECT {duck: 42}::JSON; {"duck":42} This works for our nested types as shown in the example, but also for non-nested typ... - https://man.mtool.work/duckdb/2.0/data/json/json_type.html
- Quack Remote Protocol 9825
- 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
...trip per query. After the initial connection handshake, a query needs only one request–response pair. Large results stream back in chunks via follow-up FETCH requests, optionally parallelized on multiple threads. Default port: 9494 . All URIs use the...'⟨MY_QUACK_TOKEN_01234567890ABCDEF⟩', disable_ssl = true ); The query executes remotely and the server streams the result back. Errors occurring on the server (parse errors, missing tables, etc.) are shown locally in the DuckDB client. Attaching a R...ONNECT statement routes the whole session to it, so that subsequent queries execute on the server and their results stream back. This is the recommended way to work with a remote Quack database: you write plain SQL without qualifying every table name... - https://man.mtool.work/duckdb/2.0/quack/overview.html
- CONNECT and DISCONNECT Statements 9825
- 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
...xample.com' AS qk (TOKEN '⟨my_token⟩'); 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 DuckDB, the connecti... - https://man.mtool.work/duckdb/2.0/sql/statements/connect.html
- Join Operations 9600
- How to Force a Join Order DuckDB has a cost-based query optimizer, which uses statistics in the base tables (stored in a DuckDB database or Parquet files) to estimate the cardinality of operations. Turn off the Join Order Optimizer To turn
...this join is performed first JOIN ...; -- this join is performed second Once the query in question has been executed, turn back the optimizers with the following command: SET disabled_optimizers = ''; Create Temporary Tables To force a particular joi...r optimization times. Lowering it reduces optimization time for large joins. Even below the threshold, the optimizer falls back to the approximate algorithm if exact enumeration exceeds its internal budget.... - https://man.mtool.work/duckdb/2.0/guides/performance/join_operations.html
- Run Queries 9375
- Overview A Connection runs SQL through two families of methods: The execute_* methods ( execute() and execute_batch() ) send statements that do not return rows, such as INSERT or DDL, and report the number of affected rows. The query_* meth
...ods ( query() , query_map() , and query_row() ) run statements that return rows and hand each Row back to be mapped into a Rust value. Prepared statements work with both. The sections below walk through sending statements, bi...string, byte-slice, and boolean types. Option<T> maps to and from SQL NULL , so None binds as NULL and a NULL result reads back as None . Warning Do not use prepared statements to insert large amounts of data into DuckDB. See Import Data for the Appe...ent once so it can be executed repeatedly. The returned Statement can be executed with execute() , or queried to read rows back. let mut stmt = conn.prepare("INSERT INTO person (id, name) VALUES (?, ?)")?; stmt.execute(params![1, "Steven"])?; stmt.ex... - https://man.mtool.work/duckdb/2.0/clients/rust/querying.html
- Python DB API 8475
- The standard DuckDB Python API provides a SQL interface compliant with the DB-API 2.0 specification described by PEP 249 similar to the SQLite Python API . Connection To use the module, you must first create a DuckDBPyConnection object that
...n.sql(query).pl() or con.sql(query).to_arrow_reader() , which streams. Transactions con.begin() , con.commit() and con.rollback() start, commit and roll back a transaction, as the BEGIN , COMMIT and ROLLBACK statements do. Inside a transaction, any s...ansaction, including one with a syntax error or one that names a missing table. After that, commit() rolls the transaction back without raising an error, and any other statement raises a TransactionException until you roll back: con.begin() con.execu...T count(*) FROM items") _duckdb.TransactionException: TransactionContext Error: Current transaction is aborted (please ROLLBACK) con.rollback() con.execute("SELECT count(*) FROM items").fetchall() [(5,)]... - https://man.mtool.work/duckdb/2.0/clients/python/dbapi.html
- Legacy Parser Extension 8250
- New The legacy_parser extension was introduced in DuckDB 2.0. DuckDB 2.0.0 replaced the PostgreSQL-derived parser with a new PEG-based parser . The legacy_parser extension allows reverting to the old parser. The PEG parser is designed to be
...run: INSTALL AND LOAD legacy_parser; Usage To activate the legacy parser, run: SET enable_legacy_parser = true; To switch back to the PEG parser, run: SET enable_legacy_parser = false;... - https://man.mtool.work/duckdb/2.0/core_extensions/legacy_parser.html
- Command Line Client 8026
- Installation To use the DuckDB CLI client, visit the CLI installation page . The latest stable version of the DuckDB command line client is 2.0.0. Installation The DuckDB CLI (Command Line Interface) is a single, dependency-free executable.
...ath to the file containing the SQL and/or commands to execute. After running the commands in the file, control will revert back to the terminal. Output from the execution of that file is governed by the same .output and .once commands that have been...discussed previously. This allows the output to be displayed back to the terminal, as in the first example below, or out to another file, as in the second example. In this example, the fil...tilizes /dev/stdin as a file location. cat test.csv | duckdb -c "SELECT * FROM read_csv('/dev/stdin')" woot 42 43 To write back to stdout, the copy command can be used with the /dev/stdout file location. cat test.csv | \ duckdb -c "COPY (SELECT * FRO... - https://man.mtool.work/duckdb/2.0/clients/cli/overview.html
DuckDB 2.0 Documentation / man.mtool.work