We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, At the moment we are using the urlto field to check if a sgf is not already in the db.
While this work for automatic kgs games added by check_player, there could be conflict when we upload games manually.
Indeed manual upload sgf urlto field is set to the default 'http://'.
I was thinking using the BL[time] WL[time] that record the exact time (milliseconds) left for a player at a move inside a sgf.
I guess we can assume that if in 2 sgf, both 5 first move have been played at the exact same time, those are same sgf;
So creating a new field 'check_code' that would be a list (or the sum?) of those could work better I think.
The text was updated successfully, but these errors were encountered:
[migrate] #5: add sgf check_code field + populate in parse + check in…
1502d65
… check
It's done, but we need to populate db now
Sorry, something went wrong.
Hum... apparently there might be a conventional way to deal with that. See here.
No branches or pull requests
Hi,
At the moment we are using the urlto field to check if a sgf is not already in the db.
While this work for automatic kgs games added by check_player, there could be conflict when we upload games manually.
Indeed manual upload sgf urlto field is set to the default 'http://'.
I was thinking using the BL[time] WL[time] that record the exact time (milliseconds) left for a player at a move inside a sgf.
I guess we can assume that if in 2 sgf, both 5 first move have been played at the exact same time, those are same sgf;
So creating a new field 'check_code' that would be a list (or the sum?) of those could work better I think.
The text was updated successfully, but these errors were encountered: