PtahBlog — Page 7
Practical guides to database schema changes with Ptah.
Prisma Models, Ptah Deployment Checks
Keep Prisma models and its typed client, export the desired PostgreSQL schema, and use Ptah to plan, verify, and deploy a new ticket-priority field and index.
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.
Moving a Go Service from golang-migrate to Ptah
Import existing SQL migration pairs, keep the old history table intact, and verify a Go queue worker against the next schema change deployed by Ptah.
From Liquibase to Ptah with a Verified Starting Point
Move a PostgreSQL subscription service from a Liquibase SQL changelog to Ptah, preserving its data and checking the imported rollback before the next change.
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.
From Flyway to Ptah Without Replaying Production
Import a Flyway history, verify it against an existing PostgreSQL database, and let Ptah apply the next change while preserving the application's data.
Shipping a Schema Through Harbor by Digest
Publish a schema to Harbor with Ptah, promote the same artifact, and prove that a digest-pinned Kubernetes deployment changes only when you select new content.
A Big Update to the Ptah Playground
The real Ptah CLI in your browser tab, against SQLite. What's new: guided steps, change marks in the editor, and a layout for phones.
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.
Your First Schema Change with the Ptah Kubernetes Operator
Publish a shipment schema with Ptah, inspect the operator's plan, approve that exact change, and verify the database has converged.