APromptAura

#migration

Top prompts tagged migration.

0
p/codingAauraNovice4 days agohas example⁂auto-checked

SQL migration scripts with a tested rollback path

Write a database migration for: change_description in database. I need both the forward migration and a working rollback, not just a comment saying 'reverse the above'. Format: 1. Forward migration SQL, in the smallest safe steps (see note on locking below). 2. Rollback SQL that actually restores the prior state, including data if the forward migration transforms or deletes anything (not just structural revert). If perfect rollback is impossible (e.g. a dropped column's data is gone), say so explicitly and propose a mitigation (e.g. rename instead of drop, keep for one release cycle). 3. State which statements take a table lock and roughly how that scales with table size, using database's actual locking behavior, not a generic claim. 4. Idempotency: write the migration so re-running it after a partial failure doesn't error out (use IF NOT EXISTS / IF EXISTS guards where the dialect supports them). 5. A one-line comment above each statement explaining its purpose, for the next engineer reading the migration file. Current schema: schema Change needed: change_description
ClaudeGPT#sql#migration#database#rollback
0
0
p/codingAauraNovice4 days agohas example⁂auto-checked

Zero-downtime database schema migration plan

I need to make this schema change: change_description on table table_name in database (production, actively serving traffic, row_count rows). Produce a plan that avoids locking the table for writes and avoids breaking currently-deployed application code during the rollout. Structure: 1. Break the change into safe, backward-compatible steps (e.g. add-nullable-column before backfill before add-constraint before drop-old-column), each deployable independently. 2. For each step, specify: the exact DDL, whether it takes a lock and for how long is acceptable, and what application code version must already be deployed before this step runs. 3. Backfill strategy: batched, with a way to pause/resume, and an estimate of how long it will take given the row count. 4. The order in which application code changes and migration steps must be deployed relative to each other (expand/contract pattern), stated explicitly as a sequence. 5. A rollback plan for each step that doesn't require restoring from backup. 6. What to monitor during the backfill (replication lag, lock wait time, error rate) to know if it's safe to keep going.
ClaudeGPT#sql#migration#database#production
0
0
p/codingAauraNovice4 days agohas example⁂auto-checked

Plan a legacy framework migration with a reversible, staged rollout

I need to migrate codebase_description from old_framework to new_framework. Produce a migration plan, not code, structured as: 1. Inventory: what categories of code/config depend on the old framework's specific behavior (not just imports, actual behavioral coupling like implicit type coercion, routing conventions, middleware order). 2. Strangler-fig staging: an order of migration that lets old and new run side by side, with the riskiest, most-coupled piece migrated last, not first. 3. For each stage, a concrete rollback trigger (a metric or error class, not 'if it feels wrong') and how to revert that stage specifically without reverting the whole migration. 4. Testing strategy per stage: what must have parity tests before cutover versus what can be verified by monitoring after. 5. A list of behavioral differences between old_framework and new_framework that commonly cause silent bugs during this exact migration, so I know what to watch for. Do not recommend a big-bang rewrite unless you can justify why staging is not possible here.
ClaudeGPT#migration#architecture#rollout-strategy
0