Results of 1 - 10 of about 50 for versions (0.002 sec.)
- Storage Versions and Format 15656
- Compatibility Backward Compatibility Backward compatibility refers to the ability of a newer DuckDB version to read storage files created by an older DuckDB version. Version 0.10 is the first release of DuckDB that supports backward compati
...e format. DuckDB 0.10 can read and operate on files created by the previous DuckDB version – DuckDB 0.9. For future DuckDB versions, our goal is to ensure that any DuckDB version released after can read files created by previous versions, starting from t...to read the files without having to worry about which version the file was written with or having to convert files between versions. Forward Compatibility Forward compatibility refers to the ability of an older DuckDB version to read storage files produc...to the storage format in the future. As such, forward compatibility may be (partially) broken on occasion. Warning DuckDB versions before 2.0 cannot read database files that use the v2.0.0 storage format, which DuckDB 2.0 uses by default for new databas... - https://man.mtool.work/duckdb/2.0/internals/storage.html
- Migrating to DuckDB 2.0 10723
- DuckDB 2.0.0 is packed with new features and performance improvements, including query optimization and asynchronous I/O. It also ships a small set of breaking changes, most notably a new default storage format, which DuckDB versions before
...t common source of issues to be the storage format, which is described first below. Breaking Changes Storage Format DuckDB versions before 2.0.0 cannot read database files that use the DuckDB 2.0.0 storage format. By default, every new database file crea...ersion 69 ). The other direction keeps working: DuckDB 2.0.0 can read and write existing database files created by earlier versions. These files keep their storage version when v2.0.0 writes to them, so they remain readable by the earlier version. For ex...);" ~/.duckdb/cli/1.5.6/duckdb my.db IO Error: Trying to read a database file with version number 69, but we can only read versions between 64 and 68. The database file was created with a newer version of DuckDB. Newer DuckDB version might introduce back... - https://man.mtool.work/duckdb/2.0/operations_manual/migration.html
- Release Cycle 10151
- 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>.<
...MINOR>.<PATCH> ) Feature releases (new minor or major versions) are released approximately every 6 months, e.g., v1.4.0 in September 2025, v1.5.0 in March 2026 and v2.0.0 in October 202...6 Patch releases are issued as needed for all supported versions: The latest stable version Long Term Support (LTS) versions within their support period Versions with extended support (e....of-life dates are listed in the Release Calendar Terminology In the release docs we use some basic terminology to describe versions and branches. We briefly go over them here. vx.y.z : The latest stable release vx.y-codename : The name of the branch that... - https://man.mtool.work/duckdb/2.0/dev/release_cycle.html
- DuckLake 10061
- DuckLake 1.1 was released together with DuckDB 2.0. Read the announcement blog post . The ducklake extension adds support for attaching to databases stored in the DuckLake format . The complete documentation of this extension is available a
...le_insertions The ducklake_table_insertions function returns the rows inserted in a given table between snapshots of given versions or timestamps. The function has two variants, depending on whether start_snapshot and end_snapshot have types BIGINT or TI...ble_deletions The ducklake_table_deletions function returns the rows deleted from a given table between snapshots of given versions or timestamps. The function has two variants, depending on whether start_snapshot and end_snapshot have types BIGINT or TI...ake_table_changes The ducklake_table_changes function returns the rows changed in a given table between snapshots of given versions or timestamps. The function has two variants, depending on whether start_snapshot and end_snapshot have types BIGINT or TI... - https://man.mtool.work/duckdb/2.0/core_extensions/ducklake.html
- ATTACH and DETACH Statements 9384
- DuckDB allows attaching to and detaching from database files. Examples Attach the database file.db with the alias inferred from the name ( file ): ATTACH 'file.db'; Attach the database file.db with an explicit alias ( file_db ): ATTACH 'fil
...uckdb' AS stations_db; ATTACH 's3://⟨blobs-duckdb⟩/databases/stations.duckdb' AS stations_db (READ_ONLY); Explicit Storage Versions DuckDB 1.2.0 introduced the STORAGE_VERSION option , which allows explicitly specifying the storage version. This setting...the database file. When database files are written with this option, the resulting files cannot be opened by older DuckDB versions than the specified version. They can be read by the specified version and all newer versions of DuckDB. Since DuckDB 2.0.0...se the latest storage version by default (equivalent to STORAGE_VERSION 'latest' ), so they cannot be read by older DuckDB versions. Therefore, the main use of this option is to create database files that remain readable by older DuckDB versions: ATTACH... - https://man.mtool.work/duckdb/2.0/sql/statements/attach.html
- Versioning of Extensions 8723
- Extension Versioning Most software has some sort of version number. Version numbers serve a few important goals: Tie a binary to a specific state of the source code Allow determining the expected feature set Allow determining the state of t
...le. Unstable extensions are tagged with the short git hash of the extension. For example, an unstable extension may have a version such as 690bfc5 . What to expect from an extension that has a version number in the unstable format? The state of the sourc...s extension's API could change with every release This extension may not follow a structured release cycle, new (breaking) versions can be pushed at any time Pre-Release Extensions Pre-release extensions are the next step up from Unstable extensions. The...y are tagged with version in the SemVer format, more specifically, those in the v0.y.z format. In semantic versioning, versions starting with v0 have a special meaning: they indicate that the more strict semantics of regular ( >v1.0.0 ) versions do n... - https://man.mtool.work/duckdb/2.0/extensions/versioning_of_extensions.html
- Deploy as Native Image 8301
- 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
...command line tools, serverless functions, and small containers. Recent driver versions ship the JNI reachability metadata that native-image needs, and the build picks it up automatically from the class path. T...wo things remain for the application to configure: native access and the location of DuckDB's shared library. Driver versions up to and including 1.5.5 do not ship this metadata. For those versions, generate it by running the application once on th... - https://man.mtool.work/duckdb/2.0/clients/java/deploy_native_image.html
- Iceberg Options 8301
- 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
...N false When reading V3 Deletion Vectors, skip the Puffin file verification (for compatibility with files written by older versions). iceberg_use_metadata_log BOOLEAN true Use a table's optional metadata-log to preserve atomicity guarantees, at the cost...IMESTAMP NULL Access snapshot with a specific timestamp version VARCHAR NULL (use version-hint.text ) Provides an explicit version string, a version hint file, or '?' to guess the latest version (see Selecting Metadata Versions ) version_name_format VARC...HAR 'v%s%s.metadata.json,%s%s.metadata.json' Controls how versions are converted to metadata file names iceberg_snapshots does not take allow_moved_paths , snapshot_from_id or snapshot_from... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/iceberg_options.html
- CHECKPOINT Statement 8226
- The CHECKPOINT statement synchronizes data in the write-ahead log (WAL) to the database data file. Examples Synchronize data in the default database: CHECKPOINT; Synchronize data in the specified database: CHECKPOINT file_db; Synchronize da
...ta and prevent new transactions from starting: FORCE CHECKPOINT; In earlier DuckDB versions, FORCE CHECKPOINT aborted any in-progress transactions. From v1.4, it waits until it can grab the checkpoint lock. Checkpo...ions. Including FORCE will wait until it can grab the checkpoint lock and then execute the checkpoint operation. In DuckDB versions before v1.4, FORCE CHECKPOINT instead aborted any in-progress transactions. Also see the related PRAGMA option for further... - https://man.mtool.work/duckdb/2.0/sql/statements/checkpoint.html
- Hugging Face Support 7715
- The httpfs extension introduces support for the hf:// protocol to access datasets hosted in Hugging Face repositories. See the announcement blog post for details. Usage Hugging Face repositories can be queried using the following URL patter
...tronomy/*.parquet' WHERE question LIKE '%planet%'; count 21 Versioning and Revisions In Hugging Face repositories, dataset versions or revisions are different dataset updates. Each version is a snapshot at a specific time, allowing you to track changes a...nd improvements. In git terms, it can be understood as a branch or specific commit. You can query different dataset versions/revisions by using the following URL: hf://datasets/⟨my_username⟩/⟨my_dataset⟩@⟨my_branch⟩/⟨path_to_file⟩ For example: SEL... - https://man.mtool.work/duckdb/2.0/core_extensions/httpfs/hugging_face.html
DuckDB 2.0 Documentation / man.mtool.work