From 519518ed6c32a9412d246803e85aaa8232f6b3e7 Mon Sep 17 00:00:00 2001 From: paul Date: Fri, 25 Jul 2025 11:37:52 +0200 Subject: [PATCH] Fix migration order by renaming init.js to 001_init.js - Renamed core/init.js to core/001_init.js to ensure it runs first - Updated detectExistingSchema() to reference 001_init.js - This fixes the issue where backup migrations tried to access app_settings table before it was created - Migrations now run in correct order: init first, then numbered The error occurred because alphabetical sorting put 029 before init, causing migrations to fail on new deployments. --- backend/migrations/core/{init.js => 001_init.js} | 0 backend/migrations/run-migrations-safe.js | 4 ++-- 2 files changed, 2 insertions(+), 2 deletions(-) rename backend/migrations/core/{init.js => 001_init.js} (100%) diff --git a/backend/migrations/core/init.js b/backend/migrations/core/001_init.js similarity index 100% rename from backend/migrations/core/init.js rename to backend/migrations/core/001_init.js diff --git a/backend/migrations/run-migrations-safe.js b/backend/migrations/run-migrations-safe.js index 5e63ddc..15cbf45 100644 --- a/backend/migrations/run-migrations-safe.js +++ b/backend/migrations/run-migrations-safe.js @@ -36,8 +36,8 @@ async function detectExistingSchema() { console.log('Detecting existing schema...'); const tableChecks = [ - { table: 'events', migration: 'init.js' }, - { table: 'photos', migration: 'init.js' }, + { table: 'events', migration: '001_init.js' }, + { table: 'photos', migration: '001_init.js' }, { table: 'photo_categories', migration: '004_add_categories_and_cms.js' }, { table: 'cms_pages', migration: '004_add_categories_and_cms.js' }, { table: 'login_attempts', migration: '015_add_login_attempts_table.js' },