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  
相关推荐
就叫_这个吧28 分钟前
Java递归方法实现面包屑导航
java·开发语言
fīɡЙtīиɡ ℡43 分钟前
AI 应用系统设计
java·开发语言·人工智能
城管不管1 小时前
重生——第十一次面试之挖财一面2026.8.19已OC
java·服务器·jvm·数据库·spring·面试·职场和发展
倔强的石头1061 小时前
向量数据库从相似度检索走向融合数据底座
数据库
今天AI了吗2 小时前
Python 基础语法(一):常量、变量、输入输出与运算符
开发语言·数据库·人工智能·python·sql·深度学习·机器学习
TELL5213 小时前
selenium webdriver 第二次初始化的异常
开发语言·python
动词ing3 小时前
【C语言】自定义函数+指针入门
c语言·开发语言·算法
重生之后端学习3 小时前
283. 移动零[简单]✅
开发语言·数据结构·算法·leetcode·职场和发展
lilian2334 小时前
Harmony os 技术实战|拼豆制图27:用单字符编码承载 50 张 70×70 图纸
前端·数据库·华为·harmonyos
皮卡丘不断更4 小时前
手机优先的 Personal Ledger:把账目、学习和复盘放到同一个入口
数据库·sqlite·fastapi·开源项目·个人效率