Broken setup with 7.4.0: no such column: "old_album_id"

[nanawel]

Lychee version

v7.4.0

Did you check the latest Lychee version?

Yes, I am using the latest version

Which PHP version are you using?

PHP 8.5

Detailed description of the problem

When starting the containers after upgrading to 7.4.0, the setups fail with the following error:

...
lychee-1  | 🔄 Running database migrations...
lychee-1  | 
lychee-1  |    INFO  Running migrations.  
lychee-1  | 
lychee-1  |   2026_02_22_090000_drop_old_album_id_from_photos ................ 9.15ms FAIL
lychee-1  | 
lychee-1  | In Connection.php line 838:
lychee-1  |                                                                                
lychee-1  |   SQLSTATE[HY000]: General error: 1 error in index idx_876e0d91137abcf after   
lychee-1  |   drop column: no such column: "old_album_id" - should this be a string liter  
lychee-1  |   al in single-quotes? (Connection: sqlite, Database: /app/database/database.  
lychee-1  |   sqlite, SQL: alter table "photos" drop column "old_album_id")

Steps to reproduce the issue

No response

Diagnostics [REQUIRED]

Cannot run: startup fails

Browser & System [REQUIRED]

Standard Docker Compose stack

Please confirm (incomplete submissions will not be addressed)

• I have provided easy and step-by-step instructions to reproduce the bug.
• I understand my bug report will be removed if I haven't met the criteria above.
• I understand that if I am requested to provide more information, I must do so within 14 days or the bug report will be closed.

[ildyria]

WTF O.O
I literally migrated my containers without issues. Did it crash in the middle of the migration ?

What database setup do you have ? pgsql ? Mariadb?

[ildyria]

I will create a test setup to try to reproduce this.

[ildyria]

I rolled back to version 6.7.2, created an album, uploaded a photo, migrated to 7.4 without issue on sqlite. >_<

[nanawel]

Yes it's SQLite indeed. I don't know where it could come from 😕
I have a croned script that upgrades the app every night to the latest tag, so it cannot be an issue with a missed upgrade.

Rolling back to v7.3.3 allows the app to boot again.

[nanawel]

"Solved" with a DROP INDEX idx_876e0d91137abcf; executed directly on the DB before restarting the stack.

Strangely (and inexplicably) the error message is printed again during the migrations on the next start, but it doesn't crash anymore and the app starts eventually.

[ildyria]

That is so weird. >_<

[ildyria]

Fixed~ish.