Phil Skentelbery 605681de42 fix: Handle partially migrated databases in migration 002 detection ...

CRITICAL HOTFIX for production deployment failure

Problem:
- Production database had migration 001 applied but not migration 002
- Migration 002's tables (tokens, authorization_codes) already existed from SCHEMA_SQL
- Smart detection only checked when migration_count == 0 (fresh database)
- For partially migrated databases (count > 0), tried to run full migration
- This failed with "table already exists" error

Solution:
- Always check migration 002's state, regardless of migration_count
- If tables exist with correct structure, skip table creation
- Create missing indexes only
- Mark migration as applied

Testing:
- Manual verification with production scenario: SUCCESS
- 561 automated tests passing
- test_run_migrations_partial_applied confirms fix works

Impact:
- Fixes deployment on partially migrated production databases
- No impact on fresh or fully migrated databases
- Backwards compatible with all database states

Version: 1.0.0-rc.2 → 1.0.0-rc.3

Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

2025-11-24 13:26:15 -07:00

4.3 KiB

Raw Blame History

View Raw