Why does the “Database Findings” tab in the “Coach” window sometimes show different results for the same position?
The results in this window are generated from a key based on the actual ORDER of the moves played, rather than the current position. So, if a position was arrived at by two different move orders, then the results displayed in the Database Findings tab may be different. This is due to the necessity for speed in updating the results of the Database Findings tab. A “key search” is MUCH faster than a position search of the database (a few seconds compared to a minute or more), but a position search will likely find more games in the database due to the fact that many keys may share the same position. Therefore, if you want the most accurate results, you should go to the Database Room and perform a position search based on the current position in the Game Room.
There are two reasons for this. The first is that the results in this window are generated from a key based on the actual ORDER of the moves played, rather than the current position. So, if a position was arrived at by two different move orders, then the results displayed in the Database Findings tab may be different. This is due to the necessity for speed in updating the results of the Database Finding tab. A key search is MUCH faster than a position search of the database (a few seconds compared to a minute or more), but a position search will likely find more games in the database due to the fact that many keys may share the same position. Therefore, if you want the most accurate results, you should go to the Database Room and perform a position search based on the current position in the Game Room. The second reason is that there is a bug in this window that involves games with threaded move lists. Threaded move lists confuse the Database Findings portion of the code, thereby produ
