⌘K ctrl+k
Search Shortcut cmd + k | ctrl + k
DuckDB 2.0 ドキュメント 全文検索
per page, with , order by , clip by
Results of 1 - 2 of about 2 for codename (0.001 sec.)
Release Cycle 11228
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>.< ... 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 will produce vx.y.<n> releases vx.<y+1>-codename : The branch name that is used for the bran ... ng vx.<y+1>.0 and vx.y.<z+1> releases Active branch : A branch that is part of the main release cycle. Either main or vx. -codename where n >= 0 Single branch extension : Extension with 1 active branch. Since main is always an active branch this is alway ... s main. This means all other branches of format vx.y-codename must be vx.<y-n>-codename where n >= 1 Multi branch extension : Extension with more than 1 active branch Two branch extens ...
https://man.mtool.work/duckdb/2.0/dev/release_cycle.html
DuckDB Environment 7485
DuckDB provides a number of functions and PRAGMA options to retrieve information on the running DuckDB instance and its environment. Version The version() function returns the version number of DuckDB. SELECT version() AS version; version v ... 2.0.0 Using a PRAGMA : PRAGMA version; library_version source_id codename v2.0.0 d54cbbe3df Cyanoptera Platform The platform information consists of the operating system, system architecture, and, ...
https://man.mtool.work/duckdb/2.0/guides/meta/duckdb_environment.html
PREV 1 NEXT
DuckDB 2.0 Documentation / man.mtool.work