Databases
Check release-line evidence, choose the correct dialect and URL, and open engine-specific operating guidance.
Start with measured support, then open the guide for the target engine. A dialect name tells Ptah which SQL rules to use; a release-line support level tells you what this repository continuously exercises. Neither is a promise that every construct renders on every target.
Common tasks
Section titled “Common tasks”Choose by engine
Section titled “Choose by engine”The sidebar includes focused guidance for SQL Server, Oracle, ClickHouse, and distributed SQL engines. The official YDB, Spanner, and DuckDB integrations run as separate providers and document their own support scope. For built-in engines, the generated support matrix and live capability output take precedence when they disagree with an engine page.
Reference
Section titled “Reference”Database URLs and dev databases separates connection scope from disposable replay targets. Dialects and capabilities explains why an accepted dialect can still refuse a concrete construct.