Results of 1 - 10 of about 89 for Extensions (0.002 sec.)
- Extensions 10455
- DuckDB has a flexible extension mechanism that allows for dynamically loading extensions. Extensions can enhance DuckDB's functionality by providing support for additional file formats, introducing new types, and domain-specific functionali
...ty. Extensions are loadable on all clients (e.g., Python and R). Extensions distributed via the Core and Community repositories are built...he ARM64 architectures, with the exception of macOS on Intel ( osx_amd64 ), which is being phased out: in DuckDB 2.0, core extensions are still built for osx_amd64 but community extensions are no longer built for it, and DuckDB 2.1 will drop support for th...e platform. Listing Extensions To get a list of extensions, use the duckdb_extensions function: SELECT extension_name, installed, description FROM duckdb... - https://man.mtool.work/duckdb/2.0/extensions/overview.html
- Installing Extensions 10428
- 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
...sitory containing extensions built and signed by the core DuckDB team. This ensures the stability and security of the core set of extensions. These ext...ensions live in the default core repository, which points to http://extensions.duckdb.org . Besides the core repository, DuckDB also supports installing extensions from other repositories. 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 the... - https://man.mtool.work/duckdb/2.0/extensions/installing_extensions.html
- Securing Extensions 10361
- DuckDB has a powerful extension mechanism, which has the same privileges as the user running DuckDB's (parent) process. This introduces security considerations. Therefore, we recommend reviewing the configuration options listed on this page
...and setting them according to your attack models. DuckDB Signature Checks DuckDB extensions are checked on every load using the signature of the binaries. There are currently three categories of extensions: Signed...with a core key. Only extensions vetted by the core DuckDB team are signed with these keys. Signed with a community key. These are open-source extensions d...istributed via the DuckDB Community Extensions repository . Unsigned. Overview of Security Levels for Extensions DuckDB offers the following security levels for extensio... - https://man.mtool.work/duckdb/2.0/operations_manual/securing_duckdb/securing_ext...
- Versioning of Extensions 9920
- 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
...d stability (e.g., v0.0.1 is likely not very stable, whereas v13.11.0 probably is stable) Just like DuckDB itself , DuckDB extensions have their own version number. To ensure consistent semantics of these version numbers across the various extensions, Duck...DB's Core Extensions use a versioning scheme that prescribes how extensions should be versioned. The versioning scheme for Core Extensions is m...ility levels: unstable , pre-release , and stable . Let's go over each of the 3 levels and describe their format: Unstable Extensions Unstable extensions are extensions that can't (or don't want to) give any guarantees regarding their current stability, or... - https://man.mtool.work/duckdb/2.0/extensions/versioning_of_extensions.html
- Extension Distribution 9893
- Platforms Extension binaries are distributed for several platforms (see below). For platforms where packages for certain extensions are not available, users can build them from source and install the resulting binaries manually . Most offic
...ial extensions are distributed for the following platforms. Some extensions are only available on a subset of these platforms; see the in...th Qualcomm CPU Deprecated The osx_amd64 platform (macOS on Intel) is being phased out. In DuckDB 2.0, DuckDB and its core extensions are still built for osx_amd64 , but community extensions are no longer built for this platform. DuckDB 2.1 will stop suppo...rting osx_amd64 . Some extensions are distributed for the following platforms: linux_amd64_musl and linux_arm64_musl windows_amd64_mingw wasm_eh and wasm_mv... - https://man.mtool.work/duckdb/2.0/extensions/extension_distribution.html
- Load Extensions 9733
- Overview DuckDB-Wasm's (dynamic) extension loading is modeled after regular DuckDB's extension loading, with a few relevant differences due to the difference in platform. A growing subset of core, community, and external extensions is suppo
...rted. This page explains the extension format, how INSTALL and LOAD behave, autoloading, which extensions are available, signing, and how extensions are fetched and served. Format Extensions in DuckDB are binaries to be dynamica....e., the possibility for DuckDB to add extension functionality on-the-fly, is enabled by default in DuckDB-Wasm. Available Extensions A growing subset of extensions is supported for DuckDB-Wasm, spanning core extensions , community extensions , and externa...l extensions. Most are fetched on the fly when they are autoloaded or explicitly loaded, rather than being bundled into the DuckDB-Wasm... - https://man.mtool.work/duckdb/2.0/clients/wasm/extensions.html
- Statically Linking Extensions 9706
- This page is for client and binding authors, and for anyone who embeds libduckdb in their own application. It describes how statically linking extensions changed in DuckDB 2.0 and what builders on top of DuckDB need to do. This change is in
...are linked and registered, not in which API your bindings call. What Changed in DuckDB 2.0 New Link-time static linking of extensions was introduced in DuckDB 2.0. Before v2.0, the set of statically linked extensions was a compile-time decision. The source...s were compiled with knowledge of which extensions were included, so a build with CORE_EXTENSIONS='json;parquet;icu' could not reuse the object files of a build with CORE_EX...libduckdb_static.a libcore_functions_extension.a libparquet_extension.a libjson_extension.a libicu_extension.a The list of extensions to link in is now chosen when linking, not when compiling. As a follow-up, the extension loader and the built-in httplib a... - https://man.mtool.work/duckdb/2.0/dev/building/linking_extensions.html
- Release Cycle 9505
- 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>.<
...I extension : An extension targeting the unstable extension API. This can be both the C++ API or the unstable C API. These extensions are not binary-compatible across multiple DuckDB versions Stable API extension : An extension targeting the stable C API o...f DuckDB. These extensions are binary-compatible across multiple DuckDB versions In-tree extensions : Extensions that live inside the duckdb/duckdb s...rsions of the same codebase to co-exist. At DuckDB, there are two core branches that play the main role in the DuckDB (and extensions) release cycle. We will start off by listing the format these core branches come in. main branch: the main branch can mean... - https://man.mtool.work/duckdb/2.0/dev/release_cycle.html
- UPDATE EXTENSIONS 9238
- The UPDATE EXTENSIONS statement allows synchronizing the locally installed extension state with the repository that published a given extension. This statement is the recommended way to keep up to date with new features or bug fixes being r
...olled out by extension developers. Note that DuckDB extensions cannot be reloaded during runtime, therefore UPDATE EXTENSIONS does not reload the updated extensions. To use the updated...extensions, restart the process running DuckDB. Updating All Extensions To update all extensions installed for the DuckDB version of your client: UPDATE EXTENSIONS; This will iterate over the ex...AILABLE │ d3c5013 │ d3c5013 │ └────────────────┴──────────────┴─────────────────────┴──────────────────┴─────────────────┘ Extensions that are statically linked into the DuckDB binary, such as json , parquet and icu in the official DuckDB builds, are not u... - https://man.mtool.work/duckdb/2.0/sql/statements/update_extensions.html
- Building Extensions 8904
- Extensions can be built from source and installed from the resulting local binary. Building Extensions To build using extension flags, set the BUILD_EXTENSIONS flag to the list of extensions that you want to be built. For example: BUILD_EXTENSIONS
...ENSIONS='autocomplete;httpfs;icu;json;tpch' GEN=ninja make This option also accepts out-of-tree extensions such as delta : BUILD_EXTENSIONS='autocomplete;httpfs;icu;json;tpch;delta' GEN=ninja make Since DuckDB 2.0, extensions lis...ted in BUILD_EXTENSIONS are built but not statically linked into the DuckDB executable by default: they are installed from the build's own extensi...on repository and loaded on first use. To link them into the executable, set LINK_CORE_EXTENSIONS=1 or list them in STATICALLY_LINK_EXTENSIONS (see Linking Extensions ). Special Extension Flags BUILD_JEMALLOC This flag c... - https://man.mtool.work/duckdb/2.0/dev/building/building_extensions.html
DuckDB 2.0 Documentation / man.mtool.work