-
-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Labels
component:dataDatabase, Redis, etc - how we save and deal with our dataDatabase, Redis, etc - how we save and deal with our datameta:nit-pickStuff that looks important to devs but probably has minimal impact for usersStuff that looks important to devs but probably has minimal impact for userssize:SCan probably be done in a day or twoCan probably be done in a day or two
Description
There needs to be a way to deal with recorded games that turned out to be invalid.
As part of #78 some recorded games have been discovered that ended more than once. In that case, those with two recorded ending events are the invalid ones, but in other cases other rules might apply, so an automatic rule is hard to come up with. Rather they should be dealt with manually on a case-by-case basis.
Deleting them might be also be too destructive of an operation. I'd rather see them marked as invalid with a flag in the db, but that will also make any statistical queries rather complicated.
Metadata
Metadata
Assignees
Labels
component:dataDatabase, Redis, etc - how we save and deal with our dataDatabase, Redis, etc - how we save and deal with our datameta:nit-pickStuff that looks important to devs but probably has minimal impact for usersStuff that looks important to devs but probably has minimal impact for userssize:SCan probably be done in a day or twoCan probably be done in a day or two