Upstream/SongodaCore
1
0
Fork 0
mirror of https://github.com/songoda/SongodaCore.git synced 2024-10-22 12:20:26 +02:00
Code Issues Projects Releases Wiki Activity

Implement workaround for migrated SQLite databases applying migrations

Browse Source 
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)
This commit is contained in:
Christian Koop 2024-01-15 21:07:54 +01:00
parent adcf8619ec
commit 0e8f52b1be
No known key found for this signature in database
GPG Key ID: 89A8181384E010A3
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Core/src/main/java/com/craftaro/core/database/DataManager.java
View File

@ -163,7 +163,8 @@ public class DataManager {
} }
} else { } else {
// Grab the current migration version // Grab the current migration version
String selectVersion = "SELECT migration_version FROM " + this.getMigrationsTableName(); // Due to the automatic SQLite to H2 conversion that might have happened, two entries (one of them -1) might exist
String selectVersion = "SELECT migration_version FROM " + this.getMigrationsTableName() + " ORDER BY migration_version DESC LIMIT 1";
try (PreparedStatement statement = connection.prepareStatement(selectVersion)) { try (PreparedStatement statement = connection.prepareStatement(selectVersion)) {
ResultSet result = statement.executeQuery(); ResultSet result = statement.executeQuery();
result.next(); result.next();