| QUOTE (Kai Team @ September 13, 2013 06:12 am) |
| I just tested by deleting all logs in GSAK on an archived cache that we own, posting an online log on that cache using a date that made it the 6th newest log on the cache, and requesting 5 logs. The logs come in date order, not logid order (i.e. the log I just posted was not included in the first 5 logs returned by Get Recent Logs, even though it would have had the highest LogID). |
Yea, which is what I expected and means that my proposed method above would not be full proof in getting all missing logs. Knowing this subtlety I think we can all see how it is then possible to miss one of these "late entered" logs. However, I think most users could live with this. If it is 100% imperative that you have *all* the logs for a cache then unfortunately there would be no substitute for the inefficient brute force route of using the old method (enter a starting log of 1 and ending in a very large number - 999999999). You would also have to do the brute force method on a regular bases as there is no telling when one of these "late entered" logs will pop up.
It probably adds more weight to the fact we should just fetch 30 logs on the first attempt. This means we would only miss these "late entered" logs if:
1. Their dates are older than the newest log in the database
*and*
2. They are not in the 30 logs we initially fetch
