Results of 1 - 6 of about 6 for upcoming (0.001 sec.)
- Release Cycle 12247
- 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>.<
...f the release cycle, with about 75% of the time being 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,...ease Active Branches main vx.y-codename vx.<y+1>-codename Description The pre-release phase is intended to prepare for the upcoming vx.<y+1>.0 minor release. At the start of this phase, the vx.<y+1>-codename branch is created. This branch will be used to...produce the upcoming minor release and is the branch from which all subsequent vx.<y+1>.<n> patch releases are released. PRs into DuckDB Bug-fi... - https://man.mtool.work/duckdb/2.0/dev/release_cycle.html
- Quack Extension 10492
- 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
... - https://man.mtool.work/duckdb/2.0/core_extensions/quack.html
- Overview 9322
- Installation To use the DuckDB C API, download the libduckdb archive for your platform. The latest stable version of the DuckDB C API is 2.0.0. DuckDB implements a custom C API modeled somewhat following the SQLite C API. The API is contain
...started, or check out the Full API overview . C API v2 Warning The C API v2 is not yet stable. Its interface may change in upcoming releases. DuckDB 2.0 ships a revamped C API, which is considerably more powerful than its predecessor. Among others, it ex... - https://man.mtool.work/duckdb/2.0/clients/c/overview.html
- Migrating to DuckDB 2.0 8445
- 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
...fore migrating to DuckDB 2.0.0, assess whether your workload is mission-critical. For such workloads, consider waiting for upcoming patch releases, which address issues that surface shortly after a major release. To help facilitate this, the DuckDB devel...onents such as file systems and table functions to extensions. The C API v2 is not yet stable: its interface may change in upcoming releases. For background on extension stability levels, see Versioning of Extensions ; for the C API reference, see the C... - https://man.mtool.work/duckdb/2.0/operations_manual/migration.html
- I/O 7275
- Warning DuckDB ships with safe defaults. The configuration options described on this page are advanced options, so proceed with caution when changing them. Asynchronous I/O New Asynchronous I/O was introduced in DuckDB 2.0. Starting with v2
...async_threads explicitly. Read-Ahead To keep the asynchronous threads busy, DuckDB reads ahead: it schedules the reads for upcoming scan jobs (e.g., row groups in Parquet files or byte ranges in CSV files) before the worker threads need them. While a wor... - https://man.mtool.work/duckdb/2.0/data/io.html
- Versioning of Extensions 6982
- 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
...be useful when your workflow depends on a new feature, or when you need to confirm that your stack is compatible with the upcoming version. Nightly builds for extensions are slightly complicated due to the fact that currently DuckDB extensions binaries... - https://man.mtool.work/duckdb/2.0/extensions/versioning_of_extensions.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work