Fixed orphaned sessions issue when game id is changed

This commit is contained in:
MikeMaximus
2018-03-04 09:43:49 -06:00
parent b76a7dd6ab
commit 2e5fa70f58
2 changed files with 5 additions and 4 deletions
+1
View File
@@ -152,6 +152,7 @@ Public Class mgrMonitorList
sSQL &= "Hours=@Hours, Version=@Version, Company=@Company, Enabled=@Enabled, MonitorOnly=@MonitorOnly, BackupLimit=@BackupLimit, "
sSQL &= "CleanFolder=@CleanFolder, Parameter=@Parameter, Comments=@Comments, IsRegEx=@IsRegEx WHERE MonitorID=@QueryID;"
sSQL &= "UPDATE gametags SET MonitorID=@ID WHERE MonitorID=@QueryID;"
sSQL &= "UPDATE sessions SET MonitorID=@ID WHERE MonitorID=@QueryID;"
'Parameters
hshParams = SetCoreParameters(oGame)
+3 -3
View File
@@ -45,8 +45,8 @@ Linux Only:
Known Issues:
- If one or more Game IDs are changed on one computer and these changes are synced to another PC sharing the same backup folder, the local backup manifest data for the changed game(s) on that PC will be reset.
- This is intended behavior.
- If "Backup Handling" options are enabled in Settings, GBM will see any backups for the changed game(s) as new and will handle them accordingly.
- If one or more Game IDs are changed on one computer and these changes are synced to another PC sharing the same backup folder:
- The local session data on that PC for the changed game(s) will be lost.
- The local backup manifest data for the changed game(s) on that PC will be reset. GBM will see any backups for the changed game(s) as new and will handle them accordingly.
The entire version history of GBM releases is available at http://mikemaximus.github.io/gbm-web/versionhistory.html