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  
相关推荐
得助智能-垂类大模型16 小时前
多Agent平台哪家做得好?2026年企业级多智能体平台选型指南
大数据·数据库
为思念酝酿的痛16 小时前
MySQL数据库基础
数据库·mysql
HAPPY酷17 小时前
C++ 自定义内存池优化点云处理:从裸指针到 RAII 自动回收
开发语言·c++
瀚高PG实验室17 小时前
数据库使用psql及jdbc进行远程连接,不定时自动断开的解决办法
数据库·postgresql·瀚高数据库
梦帮科技17 小时前
量子纠缠网络与量子隐形传态攻防:量子中继器信道串扰、纠缠态保真度降解与量子路由劫持
开发语言·网络·人工智能·算法·自动化·php
老王IT17 小时前
C语言语法基础语法介绍
c语言·开发语言·算法
SelectDB技术团队17 小时前
从实时入库到实时可用:Apache Doris 5.0 增量计算场景与实践
数据库·人工智能·开源·agent·实时数仓·apache doris·增量计算
Wang's Blog17 小时前
Java 项目实战: 交友项目 - 发布圈子动态:数据库表和接口文档介绍
java·数据库·交友
Brilliantwxx17 小时前
【STM32】 独立看门狗 IWDG 深度详解:从硬件结构到工程实战
数据库·stm32·单片机·嵌入式硬件·mongodb
运维小斌18 小时前
麒麟 V10 部署 OceanBase:故障速查与验收清单
linux·数据库·oceanbase·麒麟