⌘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 61 for were (0.002 sec.)
SQL on Apache Arrow 12872
DuckDB can query multiple different types of Apache Arrow objects. DuckDB pushes the filters of a query that it can translate, such as comparisons, into the scan of an Arrow dataset. Arrow tables, record batches, scanners and RecordBatchRea ... ble WHERE i = 2").to_arrow_table() Apache Arrow Datasets Arrow Datasets stored as variables can also be queried as if they were regular tables. Datasets are useful to point towards directories of Parquet files to analyze large datasets. DuckDB will p ... set WHERE i = 2").to_arrow_table() Apache Arrow Scanners Arrow Scanners stored as variables can also be queried as if they were regular tables. Scanners read over a dataset and select specific columns or apply row-wise filtering. This is similar to h ... ders Arrow RecordBatchReaders are a reader for Arrow's streaming binary format and can also be queried directly as if they were tables. This streaming format is useful when sending Arrow data for tasks like interprocess communication or communicating ...
https://man.mtool.work/duckdb/2.0/guides/python/sql_on_arrow.html
Variant Functions 11813
This section describes functions that operate on the VARIANT type . New Most variant_* functions were introduced in DuckDB 2.0. The variant_extract , variant_normalize and variant_typeof functions were already available in DuckDB 1.5. Name ... n of a VARIANT value. Two VARIANT values that represent the same data normalize to the same result, regardless of how they were constructed or physically stored. This is useful when comparing or storing VARIANT values. | | Example | variant_normalize ...
https://man.mtool.work/duckdb/2.0/sql/functions/variant.html
PostgreSQL Extension Functions 10393
postgres_clear_cache postgres_configure_pool postgres_execute postgres_hstore_get postgres_hstore_to_json postgres_query read_postgres_binary postgres_clear_cache postgres_clear_cache() -> TABLE Clears cached schema entries (like table name ... ocal connections are NOT cleared by the reaper thread thread_local_cache_hits ( UBIGINT ): the number of times connections were successfully acquired from a thread-local cache without going to the main pool thread_local_cache_misses ( UBIGINT ): the ... number of times connections were not available in a thread-local cache and were taken from the main pool instead max_lifetime_millis ( UBIGINT ): maximum n ...
https://man.mtool.work/duckdb/2.0/core_extensions/postgres/functions.html
Reading Faulty CSV Files 10045
CSV files can come in all shapes and forms, with some presenting many errors that make the process of cleanly reading them inherently difficult. To help users read these files, DuckDB supports detailed error messages, the ability to skip fa ... n. Finally, the last block presents some of the options used in the scanner that can cause errors, indicating whether they were auto-detected or manually set by the user. Using the ignore_errors Option There are cases where CSV files may have multipl ... s: name age Pedro 31 One should note that the CSV Parser is affected by the projection pushdown optimization. Hence, if we were to select only the name column, both rows would be considered valid, as the casting error on the age would never occur. Fo ... cape The escape used e.g., " VARCHAR newline_delimiter The newline delimiter used e.g., \r\n VARCHAR skip_rows If any rows were skipped from the top of the file UINTEGER has_header If the file has a header BOOLEAN columns The schema of the file (i.e. ...
https://man.mtool.work/duckdb/2.0/data/csv/reading_faulty_csv_files.html
SQLite Import 9335
To run a query directly on a SQLite file, the sqlite extension is required. Installation and Loading The extension can be installed using the INSTALL SQL command. This only needs to be run once. INSTALL sqlite; To load the sqlite extension ... be attached using the ATTACH command . This allows you to query all tables stored within a SQLite database file as if they were a regular database. -- Attach the SQLite file "test.db" ATTACH 'test.db' AS test (TYPE sqlite); -- The table "tbl_name" ca ...
https://man.mtool.work/duckdb/2.0/guides/database_integration/sqlite.html
Statically Linking Extensions 8987
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 ... as introduced in DuckDB 2.0. Before v2.0, the set of statically linked extensions was a compile-time decision. The sources were compiled with knowledge of which extensions were included, so a build with CORE_EXTENSIONS='json;parquet;icu' could not re ...
https://man.mtool.work/duckdb/2.0/dev/building/linking_extensions.html
Analyzing a Git Repository 8987
You can use DuckDB to analyze Git logs using the output of the git log command . Exporting the Git Log We start by picking a character that doesn't occur in any part of the commit log (author names, messages, etc). Since version v1.2.0, Duc ... ECT unnest( message .lower() .regexp_replace('\W', ' ') .trim(' ') .string_split_regex('\W') ) AS word FROM commits; Then, we remove stopwords using a pre-defined list: CREATE TABLE stopwords AS SELECT unnest(['a', 'about', 'above', 'after', 'again', ... , 'then', 'there', 'these', 'they', 'this', 'those', 'through', 'to', 'too', 'under', 'until', 'up', 'very', 'was', 'we', 'were', 'what', 'when', 'where', 'which', 'while', 'who', 'whom', 'why', 'will', 'with', 'you', 'your', 'yours', 'yourself', 'yo ... ─┘ We see a steady growth over the years – especially considering that many of DuckDB's functionalities and clients, which were originally part of the main repository, are now maintained in separate repositories (e.g., Java , R ). Happy hacking! ...
https://man.mtool.work/duckdb/2.0/guides/snippets/analyze_git_repository.html
Versioning of Extensions 8624
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 ... automatically update all extensions to their latest version. The output will give the user information on which extensions were updated to/from which version. For example: UPDATE EXTENSIONS; extension_name repository update_result previous_version cu ... kdb/duckdb . These extensions are called in-tree. Later, the concept of out-of-tree extensions was added, where extensions were separated into their own repository, which we call out-of-tree. While from a user's perspective, there are generally no no ...
https://man.mtool.work/duckdb/2.0/extensions/versioning_of_extensions.html
TPC-DS Extension 8276
New In DuckDB 2.0, the dsdgen data generator was updated to match the TPC-DS version 4 tools. As a result, the generated data differs slightly from the data generated by DuckDB v1.x. See the related PR for more details. The tpcds extension ... o table names Pre-Generated Datasets Pre-generated DuckDB databases for TPC-DS are available for download. Note that these were generated with DuckDB v1.x. DuckDB v2.x generates slightly different TPC-DS files, compatible with TPC-DS v4. tpcds-sf10.d ...
https://man.mtool.work/duckdb/2.0/core_extensions/tpcds.html
EXPLAIN ANALYZE: Profile Queries 8276
Prepending a query with EXPLAIN ANALYZE both pretty-prints the query plan, and executes it, providing run-time performance numbers and the actual cardinality (number of rows produced) for every operator. EXPLAIN ANALYZE SELECT * FROM tbl; N ... produced and the time spent in it. Scan operators also show the number of row groups scanned and any dynamic filters that were pushed into them at runtime, e.g., by the hash join. See Also For more information, see the ”Profiling” page . ...
https://man.mtool.work/duckdb/2.0/guides/meta/explain_analyze.html
PREV 1 2 3 4 5 6 7 NEXT
DuckDB 2.0 Documentation / man.mtool.work