[GH-ISSUE #337] How to go back to 1.5.5 after unsuccesful upgrade to 2.0 rc45? #265

New issue

Closed

opened 2026-02-25 21:31:34 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 21:31:34 +03:00

Owner

Originally created by @URBANsUNITED on GitHub (Mar 7, 2021).
Original GitHub issue: https://github.com/ciur/papermerge/issues/337

Originally assigned to: @ciur on GitHub.

Hi!

How to go back to a 1.5.5 Database after an unsuccessful update to 2.0rc45?
What changes are necessary within the Database to get it work on 1.5.5 again?

Current error on the 1.5.5'er Database:

Task papermerge.core.management.commands.worker.import_from_email[64b6535a-440c-4ab6-ac97-b669aa7bc17d] raised unexpected: IntegrityError('NOT NULL constraint failed: core_page.hocr_step_0')

All is working except the import function as it seems...

If Database releated, I could add it manually with an editor. This is how I got back from 2.0 to 1.5.5

Thanks

URBANsUNITED

Originally created by @URBANsUNITED on GitHub (Mar 7, 2021). Original GitHub issue: https://github.com/ciur/papermerge/issues/337 Originally assigned to: @ciur on GitHub. Hi! How to go back to a 1.5.5 Database after an unsuccessful update to 2.0rc45? What changes are necessary within the Database to get it work on 1.5.5 again? Current error on the 1.5.5'er Database: Task papermerge.core.management.commands.worker.import_from_email[64b6535a-440c-4ab6-ac97-b669aa7bc17d] raised unexpected: IntegrityError('NOT NULL constraint failed: core_page.hocr_step_0') All is working except the import function as it seems... If Database releated, I could add it manually with an editor. This is how I got back from 2.0 to 1.5.5 Thanks URBANsUNITED

kerem

2026-02-25 21:31:34 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 21:31:34 +03:00

Author

Owner

@URBANsUNITED commented on GitHub (Mar 7, 2021):

Ok! Sorted out.
Compared the databases from 1.5.5 and 2.0 and modified them to get it working again.
Did that on MAC with DB Browser for SQLite
Solved!

BUT I still believe that the upgrading process is not proper working. If it would 100% work, it should check the database tables and indexes and add or delete them
ex.
coming from 2.0 and want to go back to 1.5.5, there are under table "core_page" the indexes hocr_step_0 - hocr_step_3 still present. deleting them for 1.5.5 will get your database back

@URBANsUNITED commented on GitHub (Mar 7, 2021): Ok! Sorted out. Compared the databases from 1.5.5 and 2.0 and modified them to get it working again. Did that on MAC with DB Browser for SQLite Solved! BUT I still believe that the upgrading process is not proper working. If it would 100% work, it should check the database tables and indexes and add or delete them ex. coming from 2.0 and want to go back to 1.5.5, there are under table "core_page" the indexes hocr_step_0 - hocr_step_3 still present. deleting them for 1.5.5 will get your database back