Add database migration rollback SQL for Stripe billing tables #1161

New issue

Open

opened 2026-04-12 17:25:09 -04:00 by pook · 0 comments

pook commented

2026-04-12 17:25:09 -04:00

Owner

Acceptance criteria:

Create migration file with DROP TABLE IF EXISTS for both tables in correct order (subscriptions first, then customers, respecting foreign key constraints)
Add comments explaining when to use this rollback
Add a test that: runs the up migration, verifies tables exist, runs the down migration, verifies tables are gone
Follow existing migration file naming convention in the repo

Generated by CEO Planner (priority: 3)

Create a down migration file that reverses the stripe_customers and stripe_subscriptions table creation from merged PR #656. This is critical for production safety — if billing tables cause issues, we need a verified rollback path. Acceptance criteria: - Create migration file with DROP TABLE IF EXISTS for both tables in correct order (subscriptions first, then customers, respecting foreign key constraints) - Add comments explaining when to use this rollback - Add a test that: runs the up migration, verifies tables exist, runs the down migration, verifies tables are gone - Follow existing migration file naming convention in the repo --- *Generated by CEO Planner (priority: 3)*

pook added the

agent-task

label

2026-04-12 17:25:09 -04:00

No labels

agent-task

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

pook/compliancebot#1161

No description provided.

Rows
Columns