You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 16, 2023. It is now read-only.
As long as we have two different sources of data, we are going to run into instances like this:
You've reviewed 0 posts today. The time between your first and last review today was 17 minutes and 29 seconds, averaging to a review every 5 minutes and 49 seconds.
Now, I know about deleted audits. If that's the case, then we still need to record it, even if we don't have all the information about it. I can make changes to the database so that the information that we don't have is not required.
@ArcticEcho what do you think about this? I would much rather have a system that says "if you want information, go ask the database."
The text was updated successfully, but these errors were encountered:
The
My Stats
commands starts with the following:This means that we use the
UserTracking
class for the main number of reviews, but the database for the actual entries (audits and table).I really think all of this information should be in one place: the database. If you want the number of audits you go to the database to query it.
As long as we have two different sources of data, we are going to run into instances like this:
Now, I know about deleted audits. If that's the case, then we still need to record it, even if we don't have all the information about it. I can make changes to the database so that the information that we don't have is not required.
@ArcticEcho what do you think about this? I would much rather have a system that says "if you want information, go ask the database."
The text was updated successfully, but these errors were encountered: