Results of 1 - 10 of about 54 for release (0.004 sec.)
- Release Cycle 14744
- 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 2026 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.g., v1.5, which is supported until March 2027) All releases and their end-of-life dates are listed in the Release Calendar Terminology In the release docs we use some basic terminol... - https://man.mtool.work/duckdb/2.0/dev/release_cycle.html
- Versioning of Extensions 13439
- 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
...ent processing of bug reports (e.g., bug #1337 was introduced in version v3.4.5 ) Allow determining chronological order of releases (e.g., version v1.2.3 is older than v1.2.4 ) Give an indication of expected stability (e.g., v0.0.1 is likely not very st...should be versioned. The versioning scheme for Core Extensions is made up of 3 different stability levels: unstable , pre-release , and stable . Let's go over each of the 3 levels and describe their format: Unstable Extensions Unstable extensions are e...n be found by looking up the hash in the extension repository Functionality may change or be removed completely with every release This extension's API could change with every release This extension may not follow a structured release cycle, new (breaki... - https://man.mtool.work/duckdb/2.0/extensions/versioning_of_extensions.html
- Installing the Python Client 9018
- Installing via Pip The Python client requires Python 3.11 or later. On Python 3.10, pip does not report an error: it installs a 1.x release instead, and with --pre a 1.x development build. The latest release of the Python client can be inst
...alled using pip . pip install duckdb The pre-release Python client (known as the “preview” or “nightly” build) can be installed using --pre . pip install duckdb --upgrade --pr... - https://man.mtool.work/duckdb/2.0/guides/python/install.html
- Handle Results 8855
- Overview DuckDB is columnar, and beyond reading a result set row by row through database/sql , the Go client can exchange whole results with Apache Arrow as a stream of record batches, and register an Arrow stream as a queryable view. Both
...to run a query and get back an array.RecordReader . Iterate it with Next() , reading one arrow.RecordBatch at a time, and release it when done: connector, err := duckdb.NewConnector("", nil) if err != nil { log.Fatal(err) } defer connector.Close() conn...r.QueryContext(context.Background(), "SELECT * FROM generate_series(1, 10)") if err != nil { log.Fatal(err) } defer reader.Release() for reader.Next() { record := reader.RecordBatch() // Process one record batch at a time. log.Printf("%d rows", record.N...er , can be registered as a DuckDB view and queried in SQL. RegisterView() takes the reader and a view name, and returns a release function that unregisters the view; call it when the view is no longer needed: release, err := ar.RegisterView(reader, "my... - https://man.mtool.work/duckdb/2.0/clients/go/result_handling.html
- Windows 8855
- On Windows, DuckDB requires the Microsoft Visual C++ Redistributable package both as a build-time and runtime dependency. Note that unlike the build process on UNIX-like systems, the Windows builds directly call CMake. Clang-cl To build Duc
...DuckDB repository: bash export GEN=ninja export CC=clang-cl export CXX=clang-cl python scripts/windows_ci.py make windows_release The make windows_release target invokes CMake with the bundled extensions configuration ( .github/config/bundled_extension...s.cmake ) and builds DuckDB in Release mode. MSYS2 and MinGW64 DuckDB on Windows can also be built with MSYS2 and MinGW64 . Note that this build is only supporte...6_64-cmake mingw-w64-x86_64-ninja git clone https://github.com/duckdb/duckdb cd duckdb cmake -G "Ninja" -DCMAKE_BUILD_TYPE=Release -DBUILD_EXTENSIONS="icu;parquet;json" cmake --build . --config Release Once the build finishes successfully, you can find... - https://man.mtool.work/duckdb/2.0/dev/building/windows.html
- Benchmark Suite 8692
- DuckDB has an extensive benchmark suite. When making changes that have potential performance implications, it is important to run these benchmarks to detect potential performance regressions. Getting Started To build the benchmark suite, ru
...epository : BUILD_BENCHMARK=1 BUILD_EXTENSIONS='tpch' make Listing Benchmarks To list all available benchmarks, run: build/release/benchmark/benchmark_runner --list Running Benchmarks Running a Single Benchmark To run a single benchmark, issue the follo...wing command: build/release/benchmark/benchmark_runner benchmark/micro/nulls/no_nulls_addition.benchmark The output will be printed to stdout in CSV f...specify an output file using the --out flag. This will write only the timings (delimited by newlines) to that file. build/release/benchmark/benchmark_runner benchmark/micro/nulls/no_nulls_addition.benchmark --out=timings.out The output will contain the... - https://man.mtool.work/duckdb/2.0/dev/benchmark.html
- Installing Extensions 8484
- 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
...For example, the core_nightly repository contains nightly builds for core extensions that are built for the latest stable release of DuckDB. This allows users to try out new features in extensions before they are officially published. Installing Extens...g ./build/debug/repository Repository created when building DuckDB from source in debug mode (for development) local_build_release ./build/release/repository Repository created when building DuckDB from source in release mode (for development) Backup Re...ns 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 the version tag of that release. For nightly DuckDB builds, it will be equal to th... - https://man.mtool.work/duckdb/2.0/extensions/installing_extensions.html
- Complete API 8366
- This page contains the reference for DuckDB's C API. The reference contains several deprecation notices. These concern methods whose long-term availability is not guaranteed as they may be removed in the future. That said, DuckDB's develope
...resent in the result object. duckdb_row_count Warning Deprecation notice. This method is scheduled for removal in a future release. Returns the number of rows present in the result object. Syntax idx_t duckdb_row_count ( duckdb_result * result ); Parame...r type of the result. duckdb_result_get_chunk Warning Deprecation notice. This method is scheduled for removal in a future release. Fetches a data chunk from the duckdb_result. This function should be called repeatedly until the result is exhausted. The...is out of bounds. duckdb_result_is_streaming Warning Deprecation notice. This method is scheduled for removal in a future release. Checks if the type of the internal result is StreamQueryResult. Syntax bool duckdb_result_is_streaming ( duckdb_result re... - https://man.mtool.work/duckdb/2.0/clients/c/api.html
- Android 8321
- DuckDB has experimental support for Android. Please use the latest main branch of DuckDB instead of the stable versions. Building the DuckDB Library Using the Android NDK We provide build instructions for setups using macOS and Android Stud
...NDROID_ABI=${ANDROID_ABI} \ -DCMAKE_TOOLCHAIN_FILE=${ANDROID_NDK}/build/cmake/android.toolchain.cmake \ -DCMAKE_BUILD_TYPE=Release ../.. cmake \ --build . \ --config Release For the arm64-v8a ABI, the build will produce the build/android_arm64-v8a/duckd..."Ninja" \ -DBUILD_EXTENSIONS="${DUCKDB_EXTENSIONS}" \ -DDUCKDB_EXPLICIT_PLATFORM=linux_arm64_android \ -DCMAKE_BUILD_TYPE=Release \ .. cmake --build . --config Release Note that you can also use the Python client on Termux: pip install --pre --upgrade... - https://man.mtool.work/duckdb/2.0/dev/building/android.html
- Run Queries 8217
- Overview DuckDB-Wasm provides functions for querying data. Queries are run sequentially: First, create a connection by calling connect . Then, run queries by calling query to materialize the whole result, or send to fetch result chunks lazi
...f await conn.send<{ v: arrow.Int }>(` SELECT * FROM generate_series(1, 100) t(v) `)) { // ... } // Close the connection to release memory await conn.close(); Prepared Statements Prepared statements let you parse a query once and run it repeatedly with d...uery(234); // ... or as result chunks for await (const batch of await stmt.send(234)) { // ... } // Close the statement to release memory await stmt.close(); // Closing the connection releases its statements as well await conn.close(); Arrow Table to JS...le to an array of JSON objects const result = arrowResult.toArray().map((row) => row.toJSON()); // Close the connection to release memory await conn.close(); Export Parquet To export a query result, write it to a Parquet file in the virtual file system... - https://man.mtool.work/duckdb/2.0/clients/wasm/query.html
DuckDB 2.0 Documentation / man.mtool.work