duckdb 1.6dev新增的.manual命令

可以模糊查询函数的文档说明。

sql 复制代码
C:\d>duckdb0711
DuckDB v1.6.0-dev10607 (Development Version, dfd8755084)
Enter ".help" for usage hints.
memory D .manual delete
No function matches 'delete'

Did you mean:
        degrees
        element_at
memory D .manual degrees
  ────────────────────────────────────────────────────────────────────────────────────────────────
  system.main                                 degrees                              scalar function

  SIGNATURE

        degrees(x DOUBLE) -> DOUBLE

  DESCRIPTION

        Converts radians to degrees

  EXAMPLES

        degrees(pi())

memory D .manual colc
No function matches 'colc'

Did you mean:
        col_description
        concat
        cos
        cot
memory D .manual concat
  ────────────────────────────────────────────────────────────────────────────────────────────────
  system.main                                  concat                              scalar function

  SIGNATURE

        concat(value ANY, ANY...) -> ANY

  DESCRIPTION

        Concatenates multiple strings or lists. `NULL` inputs are skipped. See also operator `||`.

  EXAMPLES

        concat('Hello', ' ', 'World')

        concat([1, 2, 3], NULL, [4, 5, 6])

memory D .help delete
Nothing matches 'delete'
memory D .help concat
Nothing matches 'concat'

但是不能对sql关键字查找信息。

用.help时,无法给出相应函数文档。

sqlite的rust改写tursodb也有.manual命令,但不是针对函数和命令,而是概念。

复制代码
root@DESKTOP-59T6U68:/mnt/c/d# ./tursodb061
Turso v0.6.1
Enter ".help" for usage hints.
Did you know that Turso supports a built-in MCP server? Type .manual mcp to learn more.
This software is in BETA, use caution with production data and ensure you have backups.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database
turso> .manual delete
Manual page not found: delete
turso> .manual colc
Manual page not found: colc
turso> .manual concat
Manual page not found: concat
turso> .manual materialized-views
                                                                                                                                                                             ▐
                                                                           Live Materialized Views                                                                           ▐
                                                                                                                                                                             ▐
Live materialized views in Turso are automatically updating database objects that maintain query results in real-time. Unlike traditional materialized views that require    ▐
manual refresh, Turso's live materialized views use Incremental View Maintenance (IVM) to stay current with minimal overhead.                                                ▐
                                                                                                                                                                             ▐
Enabling Materialized Views                                                                                                                                                  ▐
                                                                                                                                                                             ▐
Materialized views are an experimental feature that must be explicitly enabled:                                                                                              ▐
                                                                                                                                                                             ▐
tursodb --experimental-views your_database.db                                                                                                                                ▐
                                                                                                                                                                             ▐
What Makes Them Special                                                                                                                                                      ▐
                                                                                                                                                                             ▐
Traditional materialized views store a snapshot of query results that becomes stale as the underlying data changes. You must manually refresh them, which often means        ▐
re-executing the entire query. That is a costly operation for large datasets.                                                                                                ▐
                                                                                                                                                                             ▐
Turso's materialized views are different. They automatically update themselves by tracking only the changes to the underlying tables. When you insert, update, or delete a   ▐
row, the materialized view calculates just the incremental changes needed to stay current. This means:                                                                       ▐
                                                                                                                                                                             ▐
- No manual refresh required - Views are always up-to-date                                                                                                                   ▐
- Efficient updates - Only processes changed data, not the entire dataset                                                                                                    ▐
- Real-time consistency - Changes are reflected immediately                                                                                                                  ▐
- Scalable performance - Update cost is proportional to the size of changes, not the size of the table                                                                       ▐
                                                                                                                                                                             ▐
How Incremental View Maintenance Works                                                                                                                                       ▐
                                                                                                                                                                             ▐
Instead of re-computing the entire view when data changes, IVM tracks what has changed and updates only the affected portions of the materialized view. For example:         ▐
                                                                                                                                                                             ▐
- When you insert a new row, IVM adds only that row's contribution to the view                                                                                               ▐
- When you delete a row, IVM removes only that row's contribution                                                                                                            ▐
- When you update a row, IVM treats it as a delete of the old value followed by an insert of the new value                                                                   ▐
                                                                                                                                                                             ▐
This approach is particularly powerful for aggregations. If you have a view that calculates the sum of millions of rows, adding one new row only requires adding that single ▐
value to the existing sum---not re-summing all million rows.                                                                                                                   ▐
                                                                                                                                                                             ▐
Transactional Consistency                                                                                                                                                    ▐
                                                                                                                                                                             ▐
Because live materialized views are instantly updated, they are fully transactional. Views are updated inside the same transaction as the base table modifications, ensuring:▐
                                                                                                                                                                             ▐
- Atomic updates - View changes are committed or rolled back together with base table changes  
相关推荐
你怎么知道我是队长1 小时前
JavaScript的函数介绍
开发语言·前端·javascript
YMWM_1 小时前
python-venv虚拟环境
linux·开发语言·python
辉灰笔记1 小时前
第一篇:MySQL8.0生产备份实战|XtraBackup全自动全量+增量备份(钉钉告警+异地Binlog归档)
数据库·mysql·钉钉·运维开发
不负岁月无痕2 小时前
STL -- C++ 红黑树封装 Map 和 Set
java·c语言·开发语言·c++·面试
山峰哥2 小时前
‌Explain实战:打开数据库执行计划的黑盒‌
大数据·服务器·数据库·sql·深度优先·宽度优先
小园子的小菜2 小时前
Java核心基础:反射与泛型底层原理及实战用法详解
java·开发语言
十五年专注C++开发2 小时前
C++之std::numeric_limits介绍
开发语言·c++·limits
2501_925963382 小时前
Hi3516 + WS73 SDIO Wi-Fi 适配笔记
java·开发语言
CoderYanger2 小时前
视频切割脚本(Python版)
linux·开发语言·windows·后端·python·程序人生·职场和发展