Articles tagged “migrations” — Page 5
Guides and worked examples about migrations with Ptah.
Changing Embedding Models: Zengram Before and After Ptah
We tested a small Zengram integration that builds replacement embeddings with Ptah while old search keeps serving, then coordinates the final handover.
Replacing Atlas with Ptah: Preserve History and Reject Invalid Indexes
We tested Akashi's TimescaleDB migrations with Ptah Compat: the Atlas history stays readable, while an invalid concurrent index blocks migration success.
Atlas CE Doesn't Manage Postgres RLS. Ptah Does.
Atlas Community leaves PostgreSQL row-level security outside schema management. We tested Ptah Compat to manage tables, RLS policies, and grants together.
Generating erun's PostgreSQL Migrations with Ptah Compat
Keep erun's Atlas commands and migration history while generating PostgreSQL triggers, RLS policies, grants, and conditional role declarations.
Adding pgvector Search Without Serving Stale Embeddings
Use Ptah and a real local model to add vector search, catch source changes, test retrieval, and refuse a cutover whose evidence is out of date.
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.