⌘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 38 for Working (0.001 sec.)
Working with Huge Databases 14921
This page contains information for working with huge DuckDB database files. While most DuckDB databases are well below 1 TB, in our 2024 user survey , 1% of respondents used DuckDB files of 2 TB or more (corresponding to roughly 10 TB of CS ... rmat supports huge database files without any practical restrictions, however, there are a few things to keep in mind when working with huge database files. Object storage systems have lower limits on file sizes than block-based storage systems. For exa ... tabase takes approximately 5 seconds. On block-based storage, the file system has a significant effect on performance when working with large files. On Linux, DuckDB performs best with XFS on large files. For storing large amounts of data, consider usin ...
https://man.mtool.work/duckdb/2.0/guides/performance/working_with_huge_databases...
Files Created by DuckDB 10707
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 ~ ): ... EPOSITORY . 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 Exam ... WAL file is deleted upon exit. If DuckDB crashes, the WAL file is required to recover data. weather.duckdb.wal If you are working in a Git repository and would like to disable tracking these files by Git, see the instructions on using .gitignore for Du ...
https://man.mtool.work/duckdb/2.0/operations_manual/footprint_of_duckdb/files_cr...
Non-Deterministic Behavior 10000
Several operators in DuckDB exhibit non-deterministic behavior. Most notably, SQL uses set semantics, which allows results to be returned in a different order. DuckDB exploits this to improve performance, particularly when performing multi- ... s the cases where non-determinism is an expected behavior . If you would like to make your queries deterministic, see the “Working Around Non-Determinism” section . Set Semantics One of the most common sources of non-determinism is the set semantics use ... n executed on multiple threads, the query may return small numbers ( 0 <= z < 10e-16 ) due to floating-point inaccuracies. Working Around Non-Determinism For the majority of use cases, non-determinism is not causing any issues. However, there are some c ...
https://man.mtool.work/duckdb/2.0/operations_manual/non-deterministic_behavior.h...
Overview 9528
How is DuckDB Tested? Testing is vital to make sure that DuckDB works properly and keeps working properly. For that reason, we put a large emphasis on thorough and frequent testing: * We run a batch of small tests on every commit using GitH ...
https://man.mtool.work/duckdb/2.0/dev/sqllogictest/overview.html
marimo Notebooks 9308
marimo is an open-source reactive notebook for Python and SQL that's tightly integrated with DuckDB's Python client, letting you mix and match Python and SQL in a single git-versionable notebook. Unlike traditional notebooks, when you run a ... uns affected cells, keeping code and outputs consistent. Its integration with DuckDB makes it well-suited to interactively working with data, and its representation as a Python file makes it simple to run notebooks as scripts. Installation To get starte ... eactive SQL Cells marimo allows you to create reactive SQL cells that automatically update when their dependencies change. Working with expensive queries or large datasets? You can configure marimo's runtime to be “lazy”. By doing so, dependent cells ar ...
https://man.mtool.work/duckdb/2.0/guides/python/marimo.html
Geometry Data Type 9072
Name Description GEOMETRY Geospatial entity The GEOMETRY data type is used to store and manipulate geometric objects, such as points, lines, and polygons. The GEOMETRY type was part of the spatial extension but became a built-in data type i ... fore only available in databases using storage version v1.5 and above. However, almost all of the associated functions for working with geometries (e.g., calculating distances, areas, intersections) are still part of spatial . Types of Geometries Concep ... phic (e.g., WGS 84, which uses latitude and longitude) or projected (e.g., UTM, which uses linear units like meters). When working with geospatial data, it's important to be aware of the CRS associated with different datasets. Performing spatial operati ... kDB can use them to resolve CRS identifiers for geometry columns, but this is something we are considering for the future. Working with Geometries in Different Coordinate Reference Systems One benefit of tracking CRSs as part of the type system is that ...
https://man.mtool.work/duckdb/2.0/sql/data_types/geometry.html
Internal Errors 8836
Internal errors signal an assertion failure within DuckDB. They usually occur due to unexpected conditions or errors in the program's logic. For example, running issue 17002 on DuckDB 1.2.1 results in an internal error. INTERNAL Error: Atte ... been invalidated because of a previous fatal error. The database must be restarted prior to being used again. To continue working with the same database, start a new DuckDB session on the same database. The reason DuckDB enters “restricted mode” is bec ...
https://man.mtool.work/duckdb/2.0/dev/internal_errors.html
Release Cycle 8836
This document outlines the DuckDB and core extension release cycle framework. It is intended for developers working on DuckDB extensions to better understand the underlying processes. Overview DuckDB follows Semantic Versioning ( v<MAJOR>.< ... elease and Feature freeze . These phases are clearly defined and communicated to ensure the whole team is synchronized and working together towards the next release. Phase 1: Mid-Cycle Active DuckDB Branches main vx.y-codename Description The mid-cycle ... ng spent in this phase. It can be seen as business-as-usual , where the upcoming release is still far away and the team is working hard on merging a variety of features and bug-fixes. During this phase, patch releases ( vx.y.<z+n> ) may be created from ...
https://man.mtool.work/duckdb/2.0/dev/release_cycle.html
Unit Tester Configuration 8600
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 ... automatic checkpointing --comment <string> Extra free form comment line --data-dir <path> Root dir for test data; default WORKING_DIR/data. Relative values resolve per test cwd; absolute/remote (e.g. az://... ) values are used verbatim. --database-dest ... test name) a path level? (default on) --test-config <path> Path to a configuration file --test-dir <path> Override default working directory of test runner, available in tests as --test-env <list[struct]> The test variables, struct should have keys env_ ...
https://man.mtool.work/duckdb/2.0/dev/sqllogictest/test_configuration.html
Installing Extensions 8600
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 ... SET custom_extension_repository = 'http://extensions.duckdb-backup.org'; For details, see Backup Extension Repositories . Working with Multiple Repositories When working with extensions from different repositories, especially mixing core and core_night ...
https://man.mtool.work/duckdb/2.0/extensions/installing_extensions.html
PREV 1 2 3 4 NEXT
DuckDB 2.0 Documentation / man.mtool.work