PtahArticles tagged “releases”
Guides and worked examples about releases with Ptah.
Ptah 0.25.0 Release: From Native YDB to a Provider Platform
A visual guide to the releases since our Ptah 0.13.0 post: provider engines, safer schema changes, and clearer limits in Ptah 0.25.0.
The Hard Parts of Moving YDB into a Ptah Plugin
How we extracted YDB into a Ptah plugin, from semantic ownership and release decisions to lock failures, performance, model identity, and parity.
Add Your Database to Ptah with a Plugin
Build a database plugin on Ptah's provider API, or use the official YDB, Spanner, and DuckDB plugins. See the capabilities and a complete DuckDB example.
Qualifying Ptah Operator 0.2.4: What Broke and What We Changed
Ptah Operator 0.2.4 is accepted for production under a declared profile. This is what five releases of qualification found and what we changed.
Ptah 0.13.0: Native YDB Schemas and Migrations
Ptah 0.13.0 adds native YDB migrations and desired YQL schemas, expands dev databases, and improves locking and schema comparison across engines.
Ptah 0.12.0: Conditional PostgreSQL Roles in Desired SQL
Ptah 0.12.0 reads conditional PostgreSQL role declarations. Catch up on SQL preservation, migration loading, and container updates since 0.11.0.
Ptah 0.11.0: A Schema Plan Can Span a MySQL Server
Plan several MySQL databases together, defer PostgreSQL constraint validation, and keep index options with Ptah 0.11.0.
Ptah 0.10.0: A Dev Database Has to Be Empty
Ptah 0.10.0 refuses a dev database that holds anything its reset would drop. This post also covers Ptah 0.9.0, which had no post of its own.
Ptah 0.8.1: The Online Migration Takes a Lock Timeout
Ptah 0.8.1 runs the generated online migration under a lock timeout, and ptah-compat now applies and lints an Atlas project on TimescaleDB.
Ptah 0.8.0: Change a Schema, Then Check What It Did
What Ptah 0.8.0 adds for changing a schema under a running application and checking afterwards what the change did, and where each part stops.