可以模糊查询函数的文档说明。C:\dduckdb0711 DuckDB v1.6.0-dev10607(Development Version,dfd8755084)Enter.helpforusagehints.memory D.manualdeleteNofunctionmatchesdeleteDid you mean: degrees element_at memory D.manual degrees ──────────────────────────────────────────────────────────────────────────────────────────────── system.main degrees scalarfunctionSIGNATURE degrees(xDOUBLE)-DOUBLEDESCRIPTION Converts radianstodegrees EXAMPLES degrees(pi())memory D.manual colcNofunctionmatchescolcDid you mean: col_description concat cos cot memory D.manual concat ──────────────────────────────────────────────────────────────────────────────────────────────── system.main concat scalarfunctionSIGNATURE concat(valueANY,ANY...)-ANYDESCRIPTION Concatenates multiple stringsorlists.NULLinputs are skipped.See also operator||.EXAMPLES concat(Hello, ,World)concat([1,2,3],NULL,[4,5,6])memory D.helpdeleteNothing matchesdeletememory D.help concat Nothing matchesconcat但是不能对sql关键字查找信息。用.help时无法给出相应函数文档。sqlite的rust改写tursodb也有.manual命令但不是针对函数和命令而是概念。rootDESKTOP-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, Tursos 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. ▐ ▐ Tursos 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 rows contribution to the view ▐ - When you delete a row, IVM removes only that rows 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