paul/picpeak
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Fix migration order by renaming init.js to 001_init.js
Mirror to GitHub / mirror (push) Successful in 25s
Details
Test and Lint / backend-test (push) Successful in 1m23s
Details
continuous-integration/drone/push Build is passing
Details
Test and Lint / frontend-test (push) Successful in 2m5s
Details
Version and Release / version-bump (push) Failing after 39s
Details
Version and Release / trigger-drone (push) Has been skipped
Details

Browse Source 
- 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.
This commit is contained in:
paul
2025-07-25 11:37:52 +02:00
parent 8a0a4436b0
commit 519518ed6c
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
backend/migrations/core/init.js → backend/migrations/core/001_init.js
View File
backend/migrations/run-migrations-safe.js
+2 -2
View File
@@ -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' },