motherduck-duckdb-sql

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use this skill when you need exact DuckDB syntax, function behavior, or a quick sanity check that a statement will actually work on MotherDuck.

当你需要准确的DuckDB语法、函数行为，或快速验证某条语句是否能在MotherDuck上正常运行时，可使用本技能。

Prefer current DuckDB SQL docs for language features and function semantics.
Use current MotherDuck SQL docs for MotherDuck-only commands such as shares, secrets, snapshots, and Dive operations.
Check MotherDuck version-lifecycle docs for newly released DuckDB features before promising they are available in MotherDuck.
Treat upstream DuckDB 1.5.x docs as ahead of MotherDuck unless the current MotherDuck lifecycle docs confirm the same DuckDB version and feature surface.
Distinguish upstream DuckDB current-version docs from MotherDuck-supported DuckDB versions; MotherDuck can lag upstream current for client compatibility and SQL feature support.
If the connection path matters, verify behavior against the current Postgres-endpoint docs before promising server-mode support.

优先参考最新的DuckDB SQL文档获取语言特性和函数语义相关内容。
如需了解仅MotherDuck支持的命令（如共享、密钥、快照和Dive操作），请查阅最新的MotherDuck SQL文档。
在承诺某DuckDB新特性可在MotherDuck中使用前，先查看MotherDuck版本生命周期文档。
除非当前MotherDuck生命周期文档确认其使用相同的DuckDB版本和功能范围，否则上游DuckDB 1.5.x文档的内容会领先于MotherDuck。
区分上游DuckDB当前版本文档与MotherDuck支持的DuckDB版本；出于客户端兼容性和SQL特性支持的考虑，MotherDuck的版本可能会滞后于上游当前版本。
如果连接路径会影响结果，在承诺支持服务器模式前，请根据最新的Postgres端点文档验证行为。

Write DuckDB SQL, not PostgreSQL SQL, even when the client connects through the Postgres endpoint.
Use fully qualified
```
"database"."schema"."table"
```
names once more than one database or share is in scope.
Prefer DuckDB-native constructs when they simplify the query:
```
GROUP BY ALL
```
,
```
QUALIFY
```
,
```
UNION BY NAME
```
,
```
arg_max
```
,
```
EXCLUDE
```
, and
```
REPLACE
```
.
When porting SQL from another engine, translate functions, date arithmetic, identifier quoting, and type casts explicitly instead of assuming compatibility.
For upstream DuckDB 1.5 features such as
```
VARIANT
```
, native
```
GEOMETRY
```
,
```
date_trunc
```
return-type changes, ODBC scanner behavior, or lakehouse-format changes, verify current MotherDuck support before adding them to production guidance.
Check whether the statement depends on local files, extension install/load, temporary-table behavior, or other client-only features before claiming it will work in MotherDuck.
Treat snapshot, restore, and
```
UNDROP DATABASE
```
statements as operational SQL with plan-specific retention behavior, not ordinary analytical syntax.
Treat MotherDuck SQL as an additional surface on top of DuckDB SQL, not a replacement for it.

Confirm the connection path and whether the question is about syntax, feature support, or a specific error.
Write or repair the statement in DuckDB SQL first.
Verify any MotherDuck-only command or server-mode limitation against the current docs.
If the user needs exact syntax or function details, open
```
references/SYNTAX_REFERENCE.md
```
.

```
references/SYNTAX_REFERENCE.md
```
for DuckDB data types, friendly SQL features, functions, complex types, and common MotherDuck-specific gotchas

如需了解DuckDB数据类型、易用SQL特性、函数、复杂类型以及常见MotherDuck特有问题，请查看
```
references/SYNTAX_REFERENCE.md
```