fenway

You'll take your server down easily with that kind of unnecessary workload.

It *is* inefficient -- it's lazy storage in 99% of the use cases.

You can use an UNIQUE index constraint.

That's not EXPLAIN output.

Who is going to read through 30K rows?

Actually, they're not the same thing with invalid dates.

That depends on the kind of queries you write.

You want: SELECT id FROM idtrack WHERE timestamp >= NOW() - INTERVAL 30 SECOND

Show your CREATE TABLE otuput.

Yup -- a 3 table join, then pre-process the results for pretty output.

Don't use great circle distance -- it's just unnecessarily slow.

I don't follow.

This is the wrong forum for parsing errors.

You're supposed to do both -- (2) leave the data intact, where you expect it to be, properly related and normalized; (1) is your summary table.

See here.

Even better is to pre-process the result, build a hash based on cat_name, push onto an array, and then output it. Much cleaner that way.

I don't see any INSERT statements.

Looks good to me.

That's because you included a field in your where clause that from a table that is LEFT JOIN'ed. Move "g.game_abbreviation = 'CSS'" into the on clause for the games table and you're set.

You can't have mysql do BOTH a LEFT & RIGHT JOIN at the same time.

Yup, that's the right idea.

You don't want to optimize ALL of them. You wan't to optimize the slowest & most frequently executed ones.

Maybe the ANALYZE TABLE stats are off. Or maybe that matches more the 30% of the table.

Don't dump into the target table -- make one up. Then you can SELECT using whatever criteria you want, and then use an INSERT to transfer them over to the target table.

I don't understand.