PtahArticles tagged “postgres” — Page 4
Guides and worked examples about postgres with Ptah.
Doctrine Models with Ptah: Reviewing SQL Before Deployment
Keep Doctrine entities and queries, use Ptah to review and rehearse SQL migrations, and compare the result with Doctrine's native migration workflow.
Replacing HCI's Atlas Workaround with Ptah Compat
We replaced HCI's split Atlas and psql schema deployment with one Ptah Compat desired state, preserving functions, triggers, and pgvector indexes.
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.
GORM with a Reviewed Ptah Migration
Move schema changes out of a Go application's startup, adopt its existing GORM database with Ptah, and deploy a reviewed change before starting the new code.
SQLAlchemy Models, Ptah Migration Review
Turn an Alembic development schema into a reviewed Ptah migration, then catch a missing database default that successful SQLAlchemy inserts can hide.
Atlas CE Drop-In Replacement: What ptah-compat Found in wpmgr
We ran ptah-compat, an Atlas CE drop-in replacement, on wpmgr. It wrote an RLS policy migration Atlas CE skipped, and found schema.sql out of date.
The Ptah Playground Now Runs PostgreSQL
play.ptah.run now runs PostgreSQL 18.3 in your browser tab through PGlite. A new scenario queries JSONB, then plans and applies a GIN index 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.