Results of 1 - 10 of about 48 for require (0.001 sec.)
- Catch C/C++ Tests 16585
- While we prefer the sqllogic tests for testing most functionality, for certain tests only SQL is not sufficient. This typically happens when you want to test the C++ API. When using pure SQL is really not an option it might be necessary to
...storage_database); { // create a database and insert values DuckDB db(storage_database, config.get()); Connection con(db); REQUIRE_NO_FAIL(con.Query("CREATE TABLE test (a INTEGER, b INTEGER);")); REQUIRE_NO_FAIL(con.Query("INSERT INTO test VALUES (11, 2...2), (13, 22), (12, 21), (NULL, NULL)")); REQUIRE_NO_FAIL(con.Query("CREATE TABLE test2 (a INTEGER);")); REQUIRE_NO_FAIL(con.Query("INSERT INTO test2 VALUES (13), (12), (11...i++) { DuckDB db(storage_database, config.get()); Connection con(db); result = con.Query("SELECT * FROM test ORDER BY a"); REQUIRE(CHECK_COLUMN(result, 0, {Value(), 11, 12, 13})); REQUIRE(CHECK_COLUMN(result, 1, {Value(), 22, 21, 22})); result = con.Que... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/catch.html
- sqllogictest Introduction 10875
- For testing plain SQL, we use an extended version of the SQL logic test suite, adopted from SQLite . Every test is a single self-contained file located in the test/sql directory. To run tests located outside of the default test directory, s
...th of the temporary testing directory. statement ok COPY csv_data TO '__TEST_DIR__/output_file.csv.gz' (COMPRESSION gzip); Require & Extensions To avoid bloating the core system, certain functionality of DuckDB is available only as an extension. Tests c...an be built for those extensions by adding a require field in the test. If the extension is not loaded, any statements that occur after the require field will be skipped. Exam...ples of this are require parquet or require icu . Another usage is to limit a test to a specific vector size. For example, adding require vector_si... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/intro.html
- PostgreSQL Extension and the Secret Manager 8906
- 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
...g options are named after the corresponding connection options of libpq : HOST HOSTADDR PORT DBNAME USER PASSWORD PASSFILE REQUIRE_AUTH CHANNEL_BINDING CONNECT_TIMEOUT CLIENT_ENCODING OPTIONS APPLICATION_NAME FALLBACK_APPLICATION_NAME KEEPALIVES KEEPALI...VES_IDLE KEEPALIVES_INTERVAL KEEPALIVES_COUNT TCP_USER_TIMEOUT REPLICATION GSSENCMODE SSLMODE REQUIRESSL SSLNEGOTIATION SSLCOMPRESSION SSLCERT SSLKEY SSLKEYLOGFILE SSLPASSWORD SSLCERTMODE SSLROOTCERT SSLCRL SSLCRLDIR SSLSNI...database-1-instance-1.xxx.eu-west-1.rds.amazonaws.com" psql "host=$RDSHOST port=5432 dbname=postgres user=postgres sslmode=require password=$(aws rds generate-db-auth-token --hostname $RDSHOST --port 5432 --username postgres --region eu-west-1)" Configu... - https://man.mtool.work/duckdb/2.0/core_extensions/postgres/secrets.html
- Set Operations 8906
- Set operations allow queries to be combined according to set operation semantics . Set operations refer to the UNION [ALL] , INTERSECT [ALL] and EXCEPT [ALL] clauses. The vanilla variants use set semantics, i.e., they eliminate duplicates,
...while the variants with ALL use bag semantics. Traditional set operations unify queries by column position , and require the to-be-combined queries to have the same number of input columns. If the columns are not of the same type, casts may be...ery. DuckDB also supports UNION [ALL] BY NAME , which joins columns by name instead of by position. UNION BY NAME does not require the inputs to have the same number of columns. NULL values will be added in case of missing columns. UNION The UNION claus...e can be used to combine rows from multiple queries. The queries are required to return the same number of columns. Implicit casting to one of the returned types is performed to combine columns of di... - https://man.mtool.work/duckdb/2.0/sql/query_syntax/setops.html
- Environment 8603
- The environment where DuckDB is run has an obvious impact on performance. This page focuses on the effects of the hardware configuration and the operating system used. Hardware Configuration CPU DuckDB's officially supported architectures a
...er, there are no performance guarantees for these platforms. Memory Bestpractice Aim for 1-4 GB memory per thread. Minimum Required Memory As a rule of thumb, DuckDB requires a minimum of 125 MB of memory per thread. For example, if you use 8 threads, y...ider limiting the number of threads , e.g., by issuing: SET threads = 4; Memory for Ideal Performance The amount of memory required for ideal performance depends on several factors, including the dataset size and the queries to execute. Maybe surprising...ly, the queries have a larger effect on the memory requirement. Workloads containing large joins over many-to-many tables yield large intermediate datasets and thus require more mem... - https://man.mtool.work/duckdb/2.0/guides/performance/environment.html
- Deploy 8406
- Overview Deploying DuckDB-Wasm means serving its components so that the browser can fetch and instantiate them. This page describes each component a deployment needs to serve, how the worker and WebAssembly variants relate, how extensions a
...e-origin (sub-)domain and included at runtime Served from a third-party CDN such as jsDelivr It cannot be served as-is: it requires transpilation, because it needs to know the location of the follow-up files — the worker and WebAssembly components — in...oves performance coi targets WebAssembly with exception handling and threading, which enables parallel query execution; it requires the deployment to be cross-origin isolated (see Cross-Origin Isolation ) You can serve all three and let the library feat...s as well. When serving these files, keep the following in mind: Serve them as-is. Unlike the main library component, they require no transpilation or bundling. Serve them with the application/wasm content type so the browser can compile them efficientl... - https://man.mtool.work/duckdb/2.0/clients/wasm/deploying_duckdb_wasm.html
- Overview 8209
- DuckDB's SQL dialect is based on PostgreSQL. DuckDB tries to closely match PostgreSQL's semantics, however, some use cases require slightly different behavior. For example, interchangeability with data frame libraries necessitates order pre
... - https://man.mtool.work/duckdb/2.0/sql/dialect/overview.html
- Legacy Authentication Scheme for S3 API 8118
- 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
...ing between path-style and vhost-style URLs is possible using: SET s3_url_style = 'path'; However, note that this may also require updating the endpoint. For example for AWS S3 it is required to change the endpoint to s3.⟨region⟩.amazonaws.com . After c...⟩'; SET s3_secret_access_key = '⟨aws_secret_access_key⟩'; Alternatively, temporary S3 credentials are also supported. They require setting an additional session token: SET s3_session_token = '⟨aws_session_token⟩'; The aws extension allows for loading AW... - https://man.mtool.work/duckdb/2.0/core_extensions/httpfs/s3api_legacy_authentica...
- Securing Extensions 7921
- DuckDB has a powerful extension mechanism, which has the same privileges as the user running DuckDB's (parent) process. This introduces security considerations. Therefore, we recommend reviewing the configuration options listed on this page
...ension repositories and have picked what we think is a sensible approach: we do not attempt to review the submissions, but require that the source code of extensions is available . We do take over the complete build, sign and distribution process. Note..._extensions = false; To lock this configuration, use the lock_configuration option : SET lock_configuration = true; Always Require Signed Extensions By default, DuckDB requires extensions to be either signed as core extensions (created by the DuckDB dev... - https://man.mtool.work/duckdb/2.0/operations_manual/securing_duckdb/securing_ext...
- Unit Tester Configuration 7724
- There are three ways of setting options for the unit tester: Command Line Arguments Configuration File Environment Variables Configuration Options List See the Configuration Options List for the full list of available options. Command Line
...ring> SQL statements to execute on connection --one-initialize Initialize buffers with all 1; also see --zero-initialize --require <extension_name> If the extension is missing: fail rather than skip tests that require it --run-id <'auto'|<string>> Overr... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/test_configuration.html
DuckDB 2.0 Documentation / man.mtool.work