[stats-dev] Incremental ogr-verify
stats-dev at lists.distributed.net
stats-dev at lists.distributed.net
Fri Jun 27 15:55:05 EDT 2003
Here was my original idea. I know there are some problems, which I will
address at the end.
Load the newly retired ids and new ids into ogr_idlookup and into a separate
table
Load the data from logdata into day_results
>From the day_results and the newly retired list generate a list of affected
stub_id,nodecounts affected (call this table affected_stubs)
Delete these stubs from ogr_summary
-These should kick off triggers to update the counts in ogr_complete
Run the summary for all affected_stubs and insert these records into
ogr_summary
-These should kick off triggers to update the counts in ogr_complete
Problems:
While this is simpler from a human perspective, it is probably more work on
a daily basis
It's enbtirely possible that there couls be a stub that has been completed
with two different stubcounts. While this isn't a problem in most cases,
using triggers could make the counts be off from what they should be once
in a while unless we're very careful about checking for the stub_id in
ogr_summary.
Let me know what you think
-Nerf
More information about the stats-dev
mailing list