⌘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 64 for directory (0.002 sec.)
EXPORT and IMPORT DATABASE Statements 15191
The EXPORT DATABASE command allows you to export the contents of the database to a specific directory. The IMPORT DATABASE command allows you to then read the contents again. Examples Export the database to the target directory target_directory ... tory as CSV files: EXPORT DATABASE 'target_directory'; Export to directory target_directory , using the given options for the CSV serialization: EXPORT DATABASE 'target_direct ... ory' (FORMAT csv, DELIMITER '|'); Export to directory target_directory , tables serialized as Parquet: EXPORT DATABASE 'target_directory' (FORMAT parquet); Export to directory ... target_directory , tables serialized as Parquet, compressed with Zstd, with a ROW_GROUP_SIZE of 100,000: EXPORT DATABASE 'target_directory' ...
https://man.mtool.work/duckdb/2.0/sql/statements/export.html
Secrets Manager 10955
The Secrets manager provides a unified user interface for secrets across all backends that use them. Secrets can be scoped, so different storage prefixes can have different secrets, allowing for example to join data across organizations in ... y time DuckDB is launched. Note Persistent secrets are stored in unencrypted binary format in the ~/.duckdb/stored_secrets directory. They are protected by file system permissions (mode 600 ), similar to how SSH private keys are stored: only the user runn ... how settings worked previously. Persistent secrets are stored in unencrypted binary format in the ~/.duckdb/stored_secrets directory. On startup of DuckDB, persistent secrets are read from this directory and automatically loaded. Secret Providers To creat ... ret_key', SECRET 'my_secret_value' ); By default, this will write the secret (unencrypted) to the ~/.duckdb/stored_secrets directory. To change the secrets directory, issue: SET secret_directory = 'path/to/my_secrets_dir'; The secret_directory setting app ...
https://man.mtool.work/duckdb/2.0/configuration/secrets_manager.html
sqllogictest Introduction 10094
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 ... pecify --test-dir <root_directory> and make sure provided test file paths are relative to that root directory. The test describes a series of SQL statements ... uld run the command unittest test/sql/projection/test_simple_projection.test . If we wanted to run all tests in a specific directory, we would run the command unittest "[projection]" . Any tests that are placed in the test directory are automatically adde ... le format tests) it is necessary to create temporary files. Any temporary files should be created in the temporary testing directory. This directory can be used by placing the string __TEST_DIR__ in a query. This string will be replaced by the path of the ...
https://man.mtool.work/duckdb/2.0/dev/sqllogictest/intro.html
Deploy as Native Image 9534
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 ... g agent : bash java -agentlib:native-image-agent=config-output-dir=⟨config_dir⟩ -cp ⟨classpath⟩ ⟨MainClass⟩ Next, pass the directory to the build with -H:ConfigurationFileDirectories=⟨config_dir⟩ . Requirements GraalVM for JDK 22 or later is required. Old ... tion 1: Embed the Library in the Executable Add a resource entry naming your platform's library, either in a configuration directory passed via -H:ConfigurationFileDirectories or under META-INF/native-image in your own project: { "resources": { "includes" ... ecutable. This option produces a single self contained file, around 120 MB. The driver extracts the library to a temporary directory when the first connection opens, which adds up to a second of startup time and requires a writable temporary directory. Op ...
https://man.mtool.work/duckdb/2.0/clients/java/deploy_native_image.html
Reading Multiple Files 8974
DuckDB can read multiple files of different types (CSV, Parquet, JSON files) at the same time using either the glob syntax, or by providing a list of files to read. See the combining schemas page for tips on reading files with different sch ... ecify which Parquet files you want to read using a list parameter, glob pattern matching syntax, or a combination of both. Directory Paths The read_parquet function accepts a local directory path and recursively reads files with the .parquet extension, in ... SELECT * FROM read_parquet('dir'); This reads the same files as read_parquet('dir/**/*.parquet') . A trailing slash on the directory path is optional. In contrast, read_parquet('dir/*.parquet') reads only files directly inside dir . Files with other exten ... sions are ignored by directory discovery, even if they contain Parquet data. To read those files, supply their filenames explicitly. If the directory con ...
https://man.mtool.work/duckdb/2.0/data/multiple_files/overview.html
Command Line Client 8844
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. ... it by running tldr duckdb . Getting Started Once the CLI executable has been downloaded, decompress it and save it to any directory. Navigate to that directory in a terminal and enter the command duckdb to run the executable. If in a PowerShell or POSIX ... low, or out to another file, as in the second example. In this example, the file select_example.sql is located in the same directory as duckdb.exe and contains the following SQL statement: SELECT * FROM generate_series(5); To execute it from the CLI, the ... ds, can also be run in a single .read command. In this example, the file write_markdown_to_file.sql is located in the same directory as duckdb.exe and contains the following commands: .mode markdown .output series.md SELECT * FROM generate_series(5); To e ...
https://man.mtool.work/duckdb/2.0/clients/cli/overview.html
Installing Extensions 8787
To install core DuckDB extensions, use the INSTALL command. For example: INSTALL httpfs; This installs the extension from the default repository ( core ). Extension Repositories By default, DuckDB extensions are installed from a single repo ... POSITORY ... ... ... ... Force Installing to Upgrade Extensions When DuckDB installs an extension, it is copied to a local directory to be cached and avoid future network traffic. Any subsequent calls to INSTALL ⟨extension_name⟩ will use the local version ... PI, refer to the Client API documentation Installation Location By default, extensions are installed under the user's home directory: ~/.duckdb/extensions/⟨duckdb_version⟩/⟨platform_name⟩/ For stable DuckDB releases, the ⟨duckdb_version⟩ will be equal to ... se the extension_directories configuration option. It takes a list of directories: extensions are installed into the first directory and loaded from any of them, which is useful, e.g., for package managers or air-gapped environments: SET extension_directo ...
https://man.mtool.work/duckdb/2.0/extensions/installing_extensions.html
Files Created by DuckDB 8715
DuckDB creates several files and directories on disk. This page lists both the global and the local ones. Global Files and Directories DuckDB creates the following global files and directories in the user's home directory (denoted with ~ ): ... Y . Yes (v2.0 and later) Yes Local Files and Directories DuckDB creates the following files and directories in the working directory (for in-memory connections) or relative to the database file (for persistent connections): Name Description Example ⟨datab ... ode. The file can have any extension with typical extensions being .duckdb , .db and .ddb . weather.duckdb .tmp/ Temporary directory. Only created in in-memory mode. .tmp/ ⟨database_filename⟩.tmp/ Temporary directory. Only created in on-disk mode. weather ...
https://man.mtool.work/duckdb/2.0/operations_manual/footprint_of_duckdb/files_cr...
Configuration 8529
DuckDB has a number of configuration options that can be used to change the behavior of the system. The configuration options can be set using either the SET statement or the PRAGMA statement . They can be reset to their original values usi ... AYS allowed to be changed, even when lock_configuration is true. VARCHAR[] [] allowed_directories List of directories, and directory prefixes, that are ALWAYS allowed to be queried, even when enable_external_access is false. VARCHAR[] [] allowed_paths Lis ... VARCHAR PHYSICAL_ONLY extension_directories Set the directories to store extensions in. VARCHAR[] [] extension_repository_directory Set the directory in which trusted extension repositories are stored. This is the trust anchor for user-provided repositor ... . VARCHAR AUTO external_file_cache_spill Whether evicted external file cache blocks of remote files spill to the temporary directory instead of being dropped, so that they are re-read from there rather than re-fetched from the source. BOOLEAN false extern ...
https://man.mtool.work/duckdb/2.0/configuration/overview.html
ODBC API on Linux 8342
Driver Manager A driver manager is required to manage communication between applications and the ODBC driver. We tested and support unixODBC that is a complete ODBC driver manager for Linux. Users can install it from the command line: On De ... ql . Run the following commands with either option -u or -s to configure DuckDB ODBC. The -u option based on the user home directory to setup the ODBC init files. batch ./unixodbc_setup.sh -u The -s option changes the system level files that will be visib ... rovided. -D driver_path: the driver file path (i.e., the path for libduckdb_odbc.so), the default is using the base script directory ``` The ODBC setup on Linux is based on the .odbc.ini and .odbcinst.ini files. These files can be placed to the user home ... directory /home/⟨username⟩ or in the system /etc directory. The Driver Manager prioritizes the user configuration files over the system files. For the details of the configuration p ...
https://man.mtool.work/duckdb/2.0/clients/odbc/linux.html
PREV 1 2 3 4 5 6 7 NEXT
DuckDB 2.0 Documentation / man.mtool.work