Originally posted by PhlabibitIt does show your last finished game (as you can see if you click on the last bar), but it shows it with the rating before the end of the game. I am not sure it has always been that way, although I remember I have found it confusing before, so it probably has.
Can you see any reason why RHP won't show your last finished game in the graph? Seems silly, and causes a lot of confusion and delay.
P-
Originally posted by NordlysIt has always been that way, and it's stupied!~
It does show your last finished game (as you can see if you click on the last bar), but it shows it with the rating before the end of the game. I am not sure it has always been that way, although I remember I have found it confusing before, so it probably has.
Originally posted by mikelemagneThis poor blighter has the same problem:
What could cause that?
User 43503
Originally posted by Phlabibitbuilding a time critical db with simultaneous operations is a complex problem, and requires very specific coding practices and control down to hardware level to get it right. so, if it's not something like a banking system, where it's highly preferred that cause is before the effect, the 'unimportant' db systems are usually coded in a crude half-assed way. one that makes sure nothing silly happens, at the expense of stretching the concept of 'real time' a bit.
Can you see any reason why RHP won't show your last finished game in the graph? Seems silly, and causes a lot of confusion and delay.
P-
I don't know how the rhp database is coded, but I'd assume that's the root cause of such decisions that might look arbitrary on the surface. that and laziness to get it exactly right.
I know from experience that it can get surprisingly tricky even when there's a ready-made theoretical answer, and I doubt russ was thinking rhp would ever get this far when he coded it. so he probably did it by the seat of his pants and thought "that'll work close enough".
that's my best guess anyway.
