Christian Koop 0e8f52b1be Implement workaround for migrated SQLite databases applying migrations ... The migration version -1 is already written into the new database before the old one has been converted. This causes the migration to be run on the converted database because in addition to the migrated version (e.g. 8) the -1 is already written to the table. And now you just need to be kind of lucky to not retrieve that wrong version. Just a hacky workaround (I know)		2024-01-15 21:07:54 +01:00
..
src	Implement workaround for migrated SQLite databases applying migrations	2024-01-15 21:07:54 +01:00
pom.xml	Fix asm version again	2024-01-13 18:25:45 +01:00