@hichris A quick run through says those all look good, but: we can't just have @ThiefMaster mass-delete them, because obsolete comments almost always have comments around them that need deleted.
Picture pages! Picture pages! Time to get your picture pages!
... time to get your crayons and your pencils!
That's right, it's time to realize that you're simply not going to get anything meaningful accomplished this week, and your time would be better rewarded by joining in on the last of th...
@Undo Nah. Though an optional ?branch= parameter would be nice. Not too useful though -- I have used something similar on larger projects, but don't see a need here
@hichris123 I'm actually taking the percentage from each site, then averaging the percentages - which means that a site with a 50% accuracy rate over two handled flags has the same weight as one with a 99% rate over 2300 flags :P
(so those two sites would output 75% or something :P)
while ($row = mysql_fetch_array($query))
{
$aQuery = mysql_query("SELECT COUNT(*) AS number FROM " . $row["siteTableName"] . " WHERE handled=1 AND wasValid=1");
$bQuery = mysql_query("SELECT COUNT(*) AS number FROM " . $row["siteTableName"] . " WHERE handled=1");
// $count = $count + mysql_num_rows($aQuery);
$valid = mysql_fetch_assoc($aQuery);
$handled = mysql_fetch_assoc($bQuery);
@hichris123 nested sqls and joins are far from pretty. But putting $row elements in php sql statements that are themselves looped over a result fetch .... ick
I could probably write a nested sql statement with UNIONs and JOINs and GROUP BYs
but ... meh
when it's looping over tables that's fine. Since there are only a couple. It gets icky if you had put $row elements after the WHERE. That's when JOINs become awesome
Picture pages! Picture pages! Time to get your picture pages!
... time to get your crayons and your pencils!
That's right, it's time to realize that you're simply not going to get anything meaningful accomplished this week, and your time would be better rewarded by joining in on the last of th...
