Results of 1 - 10 of about 77 for explicitly (0.002 sec.)
- Iceberg Options 13413
- This page lists the options of the iceberg extension: the parameters accepted by the Iceberg functions , the options of the ATTACH and CREATE SECRET statements used to connect to a catalog , and the global settings. ATTACH Options To make a
...ode a warehouse or account/catalog identifier. It is normally discovered from the catalog's configuration response; set it explicitly to override. A prefix containing / is split into path components unless ENCODE_ENTIRE_PREFIX is set. NAMESPACE_SEPARATOR V...n of the ARN provided as the ATTACH path. URI s3tables.⟨region⟩.amazonaws.com/iceberg REMOVE_FILES_ON_DELETE false (unless explicitly set) STAGE_CREATE_TABLES false (unless explicitly set) PURGE_REQUESTED true (unless explicitly set) Glue When using the GL...SIGV4 URI glue.⟨region⟩.amazonaws.com/iceberg using the region from the found SECRET REMOVE_FILES_ON_DELETE false (unless explicitly set) STAGE_CREATE_TABLES false (unless explicitly set) PURGE_REQUESTED true (unless explicitly set) AWS Glue does not assi... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/iceberg_options.html
- Extensions 13247
- DuckDB has a flexible extension mechanism that allows for dynamically loading extensions. Extensions can enhance DuckDB's functionality by providing support for additional file formats, introducing new types, and domain-specific functionali
...ions (such as the CLI). Minimal embeddings that do not load any extensions by default may need to run LOAD core_functions; explicitly. Some extensions depend on it as well, for example DuckLake , which otherwise fails with an error such as Binder Error: Fa...ons . There are two main methods of making DuckDB perform the installation and loading steps for an installable extension: explicitly and through autoloading . Explicit INSTALL and LOAD In DuckDB extensions can also be explicitly installed and loaded. Both...non-autoloadable and autoloadable extensions can be installed this way. To explicitly install and load an extension, DuckDB has the dedicated SQL statements INSTALL and LOAD , which can be combined into a sin... - https://man.mtool.work/duckdb/2.0/extensions/overview.html
- Quack Extension 10995
- The quack extension adds support for the Quack remote protocol. Usage New DuckDB 2.0.0 shipped a polished version of the Quack protocol that is faster and more stable. Expect further improvements in upcoming patch releases. Quack is transpa
...rently autoinstalled and autoloaded on first use. If you would like to install Quack explicitly, run: INSTALL quack; If you would like to load Quack explicitly, run: LOAD quack; For usage details, see the Quack remote... - https://man.mtool.work/duckdb/2.0/core_extensions/quack.html
- Securing Quack with a Reverse Proxy 8923
- 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
...t'); In the client session, connect through Caddy on :8443 . Local URIs default to plain HTTP, so you have to force SSL on explicitly: {:.codebox-client} ATTACH 'quack:localhost:8443' AS quack ( TOKEN '⟨authentication_token-from-quack_serve⟩', DISABLE_SSL...nts 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:443' AS quack ( TOKEN '⟨authentication_token-from-quack_serve⟩' ); Cad...nts 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:443' AS quack ( TOKEN '⟨authentication_token-from-quack_serve⟩' );... - https://man.mtool.work/duckdb/2.0/quack/setup/reverse_proxy.html
- Typecasting 8923
- Typecasting is an operation that converts a value in one particular data type to the closest corresponding value in another data type. Like other SQL engines, DuckDB supports both implicit and explicit typecasting. Explicit Casting Explicit
...typecasting is performed by using a CAST expression. For example, CAST(col AS VARCHAR) or col::VARCHAR explicitly cast the column col to VARCHAR . See the cast page for more information. Implicit Casting In many situations, the system w...nd columns are the target type. I marks a cast the system also performs implicitly ; E marks a cast that is only available explicitly (with CAST or :: ); an empty cell marks an unsupported cast. Even where a cast is supported, it may still fail at runtime...in the future. Lossy Casts Casting operations that result in loss of precision are allowed. For example, it is possible to explicitly cast a numeric type with fractional digits – such as DECIMAL , FLOAT or DOUBLE – to an integral type like INTEGER or BIGIN... - https://man.mtool.work/duckdb/2.0/sql/data_types/typecasting.html
- FROM and JOIN Clauses 8578
- The FROM clause specifies the source of the data on which the remainder of the query should operate. Logically, the FROM clause is where the query starts execution. The FROM clause can contain a single table, a combination of multiple table
...e specified by a predicate that connects attributes from one side to attributes from the other side. The conditions can be explicitly specified using an ON clause with the join (clearer) or implied by the WHERE clause (old-fashioned). We use the l_regions...tches, not the right side (build) column values. To get the prices times in the example, you will need to list the columns explicitly: SELECT t.symbol, t.when AS trade_when, p.when AS price_when, price FROM trades t ASOF LEFT JOIN prices p USING (symbol, "...ECT * FROM t JOIN t USING(x); Binder Error: Ambiguous reference to table "memory.main.t" (duplicate alias "memory.main.t", explicitly alias one of the tables using "AS my_alias") Adding the aliases allows the query to parse successfully: SELECT * FROM t AS... - https://man.mtool.work/duckdb/2.0/sql/query_syntax/from.html
- INSERT Statement 8578
- The INSERT statement inserts new data into a table. Examples Insert the values 1, 2, 3 into tbl : INSERT INTO tbl VALUES (1), (2), (3); Insert the result of a query into a table: INSERT INTO tbl SELECT * FROM other_tbl; Insert values into t
...he i column, inserting the default value into other columns: INSERT INTO tbl (i) VALUES (1), (2), (3); Explicitly insert the default value into a column: INSERT INTO tbl (i) VALUES (1), (DEFAULT), (3); Assuming tbl has a primary key/uni...d by the VALUES clause or query are associated with the column list left-to-right. This is the default option, that can be explicitly specified using the BY POSITION option. For example: CREATE TABLE tbl (a INTEGER, b INTEGER); INSERT INTO tbl VALUES (5, 4...The table will contain the row that was first inserted: SELECT * FROM tbl; i j 1 42 These error messages can be avoided by explicitly handling conflicts. DuckDB supports two such clauses: ON CONFLICT DO NOTHING and ON CONFLICT DO UPDATE SET ... . DO NOTHIN... - https://man.mtool.work/duckdb/2.0/sql/statements/insert.html
- CREATE MACRO Statement 8246
- The CREATE MACRO statement defines a named, callable SQL expression as a database schema object. Macros may declare parameters, which can be referenced by its expression. Once a macro is created, it may be called by referencing its name and
...S [TABLE] ⟨expression⟩; The identifier consists of the macro's name, which can be any valid SQL identifier. A macro may be explicitly qualified with an existing database schema. If a schema is specified, then it appears in the usual way: before the name, w...ith a dot separating schema name and macro name. When not explicitly specified, the macro will be associated with the current schema. When connected to a persistent database file, the macro w...tempt to define multiple parameters with the same name results in a Duplicate parameter error. Optionally, a parameter may explicitly specify a particular datatype. This can be any of the existing DuckDB data types . Note: there is no way to specify a para... - https://man.mtool.work/duckdb/2.0/sql/statements/create_macro.html
- Connect 8067
- 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
...service-provider mechanism ), so no setup is needed. If that does not happen for some reason, load the DuckDBDriver class explicitly to force registration before opening a connection: Class.forName("org.duckdb.DuckDBDriver"); Connection conn = DriverManag...opens: JDBC URL Opens jdbc:duckdb: A connection-private in-memory database. jdbc:duckdb:memory: The same as above, written explicitly. jdbc:duckdb:memory:⟨label⟩ A named in-memory database that other connections can share. jdbc:duckdb:⟨path⟩ A database fil...every connection to that instance. Note that changing threads does not resize the asynchronous pool, so set async_threads explicitly as well: SET threads = 4; SET async_threads = 4; Two consequences are worth calling out for Java applications: Attached da... - https://man.mtool.work/duckdb/2.0/clients/java/connecting.html
- Deploy as Native Image 7901
- Overview The JDBC driver runs inside GraalVM Native Image executables. Graal Native Image compiles a Java application ahead of time into a standalone binary that starts in milliseconds and requires no JVM on the target machine, which suits
...-UNNAMED to native-image , or add it as a build argument in the Native Build Tools Maven or Gradle plugin. Load the driver explicitly before opening the first connection: Class.forName("org.duckdb.DuckDBDriver"); Driver auto-registration through ServiceLoa...inux_arm64 , libduckdb_java.so_osx_universal , and libduckdb_java.so_windows_amd64 . Name the one for your target platform explicitly. A wildcard matching all of them adds roughly 260 MB to the executable. This option produces a single self contained file,... - https://man.mtool.work/duckdb/2.0/clients/java/deploy_native_image.html
DuckDB 2.0 Documentation / man.mtool.work