⌘K ctrl+k
Search Shortcut cmd + k | ctrl + k
DuckDB 2.0 ドキュメント 全文検索
per page, with , order by , clip by
Results of 1 - 10 of about 127 for them (0.002 sec.)
Instantiate 10668
Overview DuckDB-Wasm can be instantiated in several ways, depending on how your application bundles and serves its assets. Each approach resolves the mainModule (the WebAssembly file) and the mainWorker (the worker script) for the browser's ... capabilities, then hands them to AsyncDuckDB . This page shows the patterns for a jsDelivr CDN, webpack, Vite and statically served files. Once instanti ... B and DuckDB-Wasm are written in C++ and use exceptions to propagate errors, so native exception handling avoids emulating them through JavaScript coi — adds threading for parallel query execution; it requires the page to be cross-origin isolated and ... ck When your application is built with webpack , let the bundler resolve and emit DuckDB-Wasm's assets instead of fetching them from a CDN. Import each .wasm module directly, and reference the worker scripts with new URL(..., import.meta.url) so that ...
https://man.mtool.work/duckdb/2.0/clients/wasm/instantiation.html
Deploy 10142
Overview Deploying DuckDB-Wasm means serving its components so that the browser can fetch and instantiate them. This page describes each component a deployment needs to serve, how the worker and WebAssembly variants relate, how extensions a ... steps depend on your setup; see the examples in the repository . For instance, the shell.duckdb.org deployment transpiles the main library together with the shell code (the first approach above), while the bare-browser example shows a minimal setup. ... nent This is distributed as a JavaScript file in three different flavors, mvp , eh and coi , and needs to be served as-is. The main library component needs to be informed of the actual location. The three variants target three different WebAssembly f ... n the same three flavors, each paired with the JS worker of the same flavor: mvp — for example duckdb-mvp.wasm , loaded by the mvp JS worker eh — for example duckdb-eh.wasm , loaded by the eh JS worker coi — for example duckdb-coi.wasm , loaded by th ...
https://man.mtool.work/duckdb/2.0/clients/wasm/deploying_duckdb_wasm.html
VALUES Clause 9432
The VALUES clause is used to specify a fixed number of rows. The VALUES clause can be used as a stand-alone statement, as part of the FROM clause, or as input to an INSERT INTO statement. Examples Generate two rows and directly return them: ... rename the columns: SELECT * FROM (VALUES ('Amsterdam', 1), ('London', 2)) cities(name, id); Generate two rows and insert them into a table: INSERT INTO cities VALUES ('Amsterdam', 1), ('London', 2); Create a table directly from a VALUES clause: CRE ...
https://man.mtool.work/duckdb/2.0/sql/query_syntax/values.html
Configuration 9261
DuckDB has a number of configuration options that can be used to change the behavior of the system. The configuration options can be set using either the SET statement or the PRAGMA statement . They can be reset to their original values usi ... 'memory_limit') AS memlimit; Or: SELECT value AS memlimit FROM duckdb_settings() WHERE name = 'memory_limit'; Examples Set the memory limit of the system to 10 GB. SET memory_limit = '10GB'; Configure the system to use 1 thread. SET threads TO 1; Tur ... LI client, the default log storage ( shell_log_storage ) prints logs to the console but cannot be queried, so we switch to the memory log storage first: SET logging_storage = 'memory'; SET enable_logging = true; SET logging_level = 'debug'; Write a s ... al threads used by the system. BIGINT GLOBAL Show a list of all available settings: SELECT * FROM duckdb_settings(); Reset the memory limit of the system back to the default: RESET memory_limit; Secrets Manager DuckDB has a Secrets manager , which pr ...
https://man.mtool.work/duckdb/2.0/configuration/overview.html
I/O 8906
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 ... to blocking I/O. As these threads spend most of their time waiting for responses (e.g., HTTP requests), there are more of them than CPU cores: by default, four times the number of system threads, capped at 256. Its size is controlled by the async_th ... eads 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 worker thread processes the current job, the asynchronous threads fetch the data for the next jobs. If the data f ... or a job has not arrived yet, the worker thread is free to run other tasks in the meantime. Keeping more fetch tasks in flight consumes more memory. To determine a budget and avoid out-of-memory issues, Du ...
https://man.mtool.work/duckdb/2.0/data/io.html
Building Extensions 8723
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_EXT ... uckDB executable by default: they are installed from the build's own extension 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 ). Spec ... DESTROY_UNPINNED_BLOCKS When previously pinned blocks in the BufferManager are unpinned, with this flag enabled we destroy them instantly to make sure that there aren't situations where this memory is still being used, despite not being pinned. DEBUG ...
https://man.mtool.work/duckdb/2.0/dev/building/building_extensions.html
Securing DuckDB 8723
DuckDB is a powerful analytical database engine. It can read and write files, access the network, load extensions, and use system resources. Like any powerful tool, these capabilities require appropriate configuration when working with sens ... . Treat these with the same caution as SQL. Recommendations: Validate and sanitize all user-provided inputs before passing them to DuckDB APIs. Apply the same sandboxing principles as for untrusted SQL when accepting input from untrusted sources. Pro ... rity-sensitive environments. Autoloading DuckDB can automatically load core extensions when certain SQL statements require them. To maintain full control over which extensions are loaded, you can disable autoloading: SET autoload_known_extensions = f ... tem operations are disabled by configuration Locking Configurations Security-related configuration settings generally lock themselves for safety reasons. For example, while we can disable community extensions using the SET allow_community_extensions ...
https://man.mtool.work/duckdb/2.0/operations_manual/securing_duckdb/overview.htm...
Appender 8380
Use an appender to insert rows that your Python code produces. It collects rows and writes them together in one SQL statement; this is called flushing. The with block below flushes on successful exit: import duckdb con = duckdb.connect() co ... s any iterable of rows. Values are converted exactly as executemany parameters are. To append to some of the columns, list them in columns . The other columns take their default value, per row: con.execute("CREATE SEQUENCE event_ids") con.execute( "C ... ws are discarded and the exception propagates. Outside a with block, call flush() to write the rows and clear() to discard them. There is no close() method. The appender remains usable after flush() , clear() or leaving a with block. Warning Garbage ... se The rows waiting to be flushed count toward DuckDB's memory_limit . When they no longer fit in memory, DuckDB can store them in temporary files. If DuckDB has no temporary directory, a full buffer makes every query on the connection raise an OutOf ...
https://man.mtool.work/duckdb/2.0/clients/python/appender.html
My Workload Is Slow 8380
If you find that your workload in DuckDB is slow, we recommend performing the following checks. More detailed instructions are linked for each point. Do you have enough memory? DuckDB works best if you have 1-4 GB memory per thread . Is you ... attached storage (NVMe SSDs). Are you using indexes or constraints (primary key, unique, etc.)? If possible, try disabling them , which boosts load and update performance. Are you using the correct types? For example, use TIMESTAMP to encode datetime ... nt of threads . Are you aware of other common issues? If so, please click the Report content issue link below and describe them along with their workarounds. ...
https://man.mtool.work/duckdb/2.0/guides/performance/my_workload_is_slow.html
Building Configuration 8197
Build Types DuckDB can be built in many different settings, most of these correspond directly to CMake but not all of them. release This build has been stripped of all the assertions and debug symbols and code, optimized for performance. de ... ilt. BUILD_EXTENSIONS='tpch;httpfs;fts;json;parquet' make More on this topic at building DuckDB extensions . Package Flags The Makefile has flags to control which components are built. These can be enabled by either setting them in the current env , ... through set up files like bashrc or zshrc , or by setting them before the call to make , for example: BUILD_BENCHMARK=1 make debug The Python, Java (JDBC) and ODBC clients are maintaine ... d in separate repositories and are no longer built from the main DuckDB repository. See the Python , Java and ODBC repositories for their build instructions. BUILD_BENCHMARK When this ...
https://man.mtool.work/duckdb/2.0/dev/building/build_configuration.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT
DuckDB 2.0 Documentation / man.mtool.work