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  
相关推荐
another heaven33 分钟前
【C/C++ Ranges 是零开销抽象吗?拆开管道、惰性求值和编译期膨胀】
c语言·开发语言·c++
星恒随风1 小时前
MySQL 从零入门(六):复合查询详解——多表查询、自连接、子查询与 UNION
linux·服务器·数据库·mysql
SomeOtherTime2 小时前
Rust 闭包语法和原理(AI回答)
开发语言·后端·rust
无奈笑天下2 小时前
银河麒麟上lsblk命令教程详解
linux·运维·服务器·数据库
apcipot_rain2 小时前
C++转Java日记(10)
java·开发语言
总要学点什么3 小时前
第105篇:三维特效-流动图片墙体效果——让箭头沿墙长滚,它俩竟是同一份代码
开发语言·javascript·ecmascript·gis·webgl·材质·cesium
xiaoye-duck3 小时前
《C++ 项目:手写大模型接入 SDK》会话模块整合:内存 SessionManager 与 DataManager 持久化联动
开发语言·数据库·c++·语言模型
AllData公司负责人4 小时前
AI大模型数据开发底座系列说明书:AllData集成DB-GPT开源项目建设 AI 多模态分析底座,涵盖模态解析/智能大屏/MCP 扩展!
大数据·数据库·人工智能·gpt·数据采集·数据接入·模态解析
2601_967987375 小时前
Sqlite参考手册
数据库·python·sqlite·api·教程
Funlang5 小时前
龙芯上的 Fun:从跑起来到机器码
开发语言·龙芯