mitai-jinkendo/backend/migrations
Lars 39d676e5c8
All checks were successful
Deploy Development / deploy (push) Successful in 43s
Build Test / lint-backend (push) Successful in 0s
Build Test / build-frontend (push) Successful in 14s
fix: migration 009 - change profile_id from VARCHAR(36) to UUID
Profile IDs are UUID type in the profiles table, not VARCHAR.
This was causing foreign key constraint error on migration.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-22 08:22:58 +01:00
..
003_add_email_verification.sql feat: add self-registration with email verification 2026-03-21 09:53:11 +01:00
004_training_types.sql feat(v9d): add training types system + logout button 2026-03-21 13:05:33 +01:00
005_training_types_extended.sql feat: add extended training types (cardio walk/dance, mind & meditation) 2026-03-21 15:16:07 +01:00
006_training_types_abilities.sql feat: admin CRUD for training types + distribution chart in ActivityPage 2026-03-21 15:32:32 +01:00
007_activity_type_mappings.sql feat: learnable activity type mapping system (DB-based, auto-learning) 2026-03-21 19:31:58 +01:00
009_sleep_log.sql fix: migration 009 - change profile_id from VARCHAR(36) to UUID 2026-03-22 08:22:58 +01:00
check_features.sql feat: v9c Phase 1 - Feature consolidation & cleanup migration 2026-03-20 18:57:39 +01:00
v9c_cleanup_features.sql feat: v9c Phase 1 - Feature consolidation & cleanup migration 2026-03-20 18:57:39 +01:00
v9c_fix_features.sql fix: add missing feature check endpoint and features 2026-03-20 12:57:29 +01:00
v9c_subscription_system.sql fix: correct UUID foreign key constraints in v9c migration 2026-03-19 12:50:12 +01:00