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  
相关推荐
xqqxqxxq6 分钟前
MySQL 数据类型笔记
数据库·笔记·mysql
techdashen9 分钟前
Go设计取舍之四: map不变时能否并发修改不同value
开发语言·后端·golang
小小小米粒17 分钟前
阿姆达尔定律(Amdahl‘s Law)
java·开发语言
知彼解己17 分钟前
Java 版本演进
java·开发语言·spring boot
风样滴男人哟22 分钟前
PHP特性之反射类ReflectionClass机制
android·开发语言·php
Logintern0929 分钟前
理解MySQL数据库的“事务与锁”
数据库·mysql
看昭奚恤哭35 分钟前
Flutter 布局核心思想
开发语言·javascript·flutter
朱容zr3331331 小时前
为什么推荐使用自增主键?使用UUID作为主键的优缺点是什么?
java·运维·数据库·后端·mysql·面试·性能优化
麻瓜code1 小时前
【Redis 】数据类型、持久化与过期删除
数据库·redis·缓存
空杆推不起1 小时前
穿透 Flink CDC 表层用法:数据库日志捕获机制、Flink Source 运行时、端到端一致性底层原理详解
大数据·数据库·flink