[SQLite Store] Every schema upgrade should process
Every schema upgrade process should fall through to the next highest version number, so they should all run, if the user has somehow upgraded their database from such an old version. Signed-off-by: Christopher Snowhill <kode54@gmail.com>
This commit is contained in:
parent
aaade58842
commit
a4f40971dd
1 changed files with 3 additions and 3 deletions
|
@ -622,7 +622,7 @@ static SQLiteStore *g_sharedStore = NULL;
|
|||
DLog(@"SQLite error: %s", error);
|
||||
return nil;
|
||||
}
|
||||
break;
|
||||
// break;
|
||||
|
||||
case 1:
|
||||
// Schema 1 to 2: Add channelconfig integer field to the knowntracks table
|
||||
|
@ -630,7 +630,7 @@ static SQLiteStore *g_sharedStore = NULL;
|
|||
DLog(@"SQLite error: %s", error);
|
||||
return nil;
|
||||
}
|
||||
break;
|
||||
// break;
|
||||
|
||||
case 2:
|
||||
// Schema 2 to 3: Add arthash blob field to the artdictionary table, requires transmutation
|
||||
|
@ -686,7 +686,7 @@ static SQLiteStore *g_sharedStore = NULL;
|
|||
}
|
||||
}
|
||||
|
||||
break;
|
||||
// break;
|
||||
|
||||
default:
|
||||
break;
|
||||
|
|
Loading…
Reference in a new issue