| GitHub | https://github.com/duckdb/duckdb |
| Website | https://duckdb.org/ |
| GitHub | https://github.com/duckdb/duckdb |
| Website | https://duckdb.org/ |
๐ฃ New post in the DuckDB tricks series
These tips can save you precious keystrokes and file scans, making both writing and running your queries faster.
For many operations, DuckDB preserves the order of rows, similarly to data frame libraries such as Pandas. Example Take the following table for example: CREATE TABLE tbl AS SELECT * FROM (VALUES (1, 'a'), (2, 'b'), (3, 'c')) t(x, y); SELECT * FROM tbl; x y 1 a 2 b 3 c Let's take the following query that returns the rows where x is an odd number: SELECT * FROM tbl WHERE x % 2 == 1; x y 1 a 3 c Because the row (1, 'a') occurs before (3, 'c') in the original table, it is guaranteed toโฆ
New blog post by Hannes Mรผhleisen and Mark Raasveldt:
Runtime-Extensible SQL Parsers Using PEG
https://duckdb.org/2024/11/22/runtime-extensible-parsers
This post, a shortened version of a CIDR 2025 paper, discusses how parsers in DBMSs could be re-designed using Parser Expression Grammars for extensibility and improved error reporting.
Despite their central role in processing queries, parsers have not received any noticeable attention in the data systems space. State-of-the art systems are content with ancient old parser generators. These generators create monolithic, inflexible and unforgiving parsers that hinder innovation in query languages and frustrate users. Instead, parsers should be rewritten using modern abstractions like Parser Expression Grammars (PEG), which allow dynamic changes to the accepted query syntax and better error recovery. In this post, we discuss how parsers could be re-designed using PEG, and validate our recommendations using experiments for both effectiveness and efficiency.
If you're curious about DuckCon, here is a talk from our previous edition, which took place in Seattle: https://www.youtube.com/watch?v=pY3fDhZiPDk
Find more info about the upcoming as well as previous DuckCon events on our website: https://duckdb.org/2025/01/31/duckcon6.html
๐ก๐ฒ๐ ๐ฟ๐ฒ๐น๐ฒ๐ฎ๐๐ฒ
We released DuckDB version 1.1.3, which is a bug fix release. You can find the change log here: https://github.com/duckdb/duckdb/releases/tag/v1.1.3
Follow our documentation for instructions on installing or upgrading: https://duckdb.org/docs/installation
๐๐ฎ๐ข.๐ฎ๐ถ ๐ฑ๐ฏ-๐ฏ๐ฒ๐ป๐ฐ๐ต๐บ๐ฎ๐ฟ๐ธ ๐๐ฝ๐ฑ๐ฎ๐๐ฒ๐ฑ
The ๐ง๐ค๐ฎ.๐บ๐ db-benchmark has been updated with new results: https://duckdblabs.github.io/db-benchmark/
You can find more details about the setup and the benchmark in our related blog posts: https://duckdb.org/2023/11/03/db-benchmark-update.html
๐ก๐ฒ๐ ๐๐๐ฒ๐บ ๐ถ๐ป ๐๐ต๐ฒ ๐ฆ๐ต๐ผ๐ฝ
As the chilly season approaches, we've got your backโliterally!
Our DuckDB hoodies are now available in the shop: https://shop.duckdb.org/. Perfect for staying warm this season!
๐๐๐ฐ ๐๐๐ฅ๐๐๐ฌ๐: ๐๐ฎ๐๐ค๐๐ ๐.๐.๐
We released DuckDB version 1.1.2, which is a bug fix release.
Curious about the change log? Here are the release notes: https://github.com/duckdb/duckdb/releases/tag/v1.1.2
Follow our documentation for instructions on installing or upgrading: https://duckdb.org/docs/installation