now thats better. How about that truant Average Opponent Rating ,"^),
Chess Changes???

Why not just incorporate a second database built around a data mart (denormalized) architecture?
The expense of rebuilding it could be offloaded via ETL style loading and would be configured for daily rebuild/reload perhaps..
In a former life I designed Data Warehouses/Marts and had my hand in ETL (extract/transform/load) frequently. If you guys want a 2nd opinion I'm happy to assist.
Matt

it's not a matter of knowing how. it's matter of getting resources to do it. all developers are currently tied up on more important matters :( i'm sorry!

No worries, I'm sure you've got plenty on your plate. If you do decide to go down the denormalized route and want to bounce something off me feel free.
Regardless, excellent work all around on the site/service.
Matt

But we have been told they will return as the current situation is temporary without putting the pressure on,perhaps a guide as to when the stats in question will return would be appreciated by all,just a rough idea would do, "Please". :-))

Yesterday it worked.
Today it is not working.
Op Av is like that.

of course new features are great !
however simply looking back at this post highlights the anoyance of these missing stats.
I currently have a rating of 1529 and i did have a avg win opp of 1300, which is considerably less than MatiSaastamoinen, whos avg win opp is much higher...
If I take my car to a garage I expect it to come back with the same amount of doors that I delivered it with, not the ability to join Live Chess tournaments!

Being a computer scientist I am quite puzzled by Eriks explanation for the average opponent component of the statistics at least.
Seriously - this only requires a few bytes of database storage per player and only updating the database after each game with a few things (in fact - just on single mysql query can do all the updating for a player).
Below is the pseudocode in case the chess.com programmers are lost..:-)
stored in database:
long avg_opp_rating_sum
long nr_of_opponents.
long avg_opp_ratting
function update_stats_after_game(opponent_rating)
{
update_database: avg_opp_rating_sum += opponent_rating
update_database: nr_of_opponents++
update_database: avg_opp_rating = avg_opp_rating_sum/nr_of_opponents
//and these 3 updates are of course packed into one single mysql update in
// real code.
}

thanks everyone for your suggestions. at this time it isn't a matter of HOW to solve it, it's a matter of having the time to do it right now.
when you have a user table with more than 3 million rows, doing an update like that isn't so simple either.
we know how to do it. we will do it. just not today :)

thanks everyone for your suggestions. at this time it isn't a matter of HOW to solve it, it's a matter of having the time to do it right now.
when you have a user table with more than 3 million rows, doing an update like that isn't so simple either.
we know how to do it. we will do it. just not today :)
Thanks for keeping us in the loop. I'll look forward to seeing it back when you end up finding the time. Until then, I'll live without it :). Keep up the hard work!

Because the former stat is almost useless in terms of rating while the latter says a great deal about someone's rating.

Because the former stat is almost useless in terms of rating while the latter says a great deal about someone's rating.
exactly.

Because the former stat is almost useless in terms of rating while the latter says a great deal about someone's rating.
exactly.
Did you read what I said? I'm completely against your idea, since Glicko RD is very useful while average opponent means almost nothing.
OK enough, this is wearisome, you win. I don't know what linear means; I was hoping you wouldn't see through me so well.
I agree. Truce.