fenway

Replication.

If you're not looking for non-matching rows, it will be much faster to user INNER JOINs.

You could always cache the resulst.

Those are some really long column names! Why are you using LEFT JOIN? In general, you need to index every column that will be used in a join -- which is typically only one of the two listed -- which ones depends on a great number of things.

Yes, but I don't see how that's an "explanation".

I mean the temp folder that mysql is set up to use. If you're concerned, then turn on the query log.

Maybe your TEMPDIR is too small / running out of space.

You really should just use a database drive to talk to another database -- CSV is horrible.

Feel free to format the ID however you'd like -- but don't corrupt the DB.

Oh, I agree, it's ugly.

I'm fairly sure ALTER TABLE does that.

This topic has been moved to PHP Coding Help. http://www.phpfreaks.com/forums/index.php?topic=352545.0

Please don't use that ever.

I thought that's what I said -- and I still prefer to set the user variable in the same statement. In terms of the last row, just UNION it in if it's not % 120.

You do understand what without locking the tables your backups are useless....

And then confirm that there isn't a mysql issue so that I can move this thread to PHP help instead.

You can initialize your user variable with a JOIN.

Not sure that I would call that "nesting" -- you can use the same expression logic that applies in a WHERE clause.

STR_TO_DATE().

You could include both in your HAVING clause.

yes, it's always safer to let the DB driver handle quoting for you.

Why not echo $sql2 so we can see.

Oh -- simply that you can use a user-variable to "number" each row, and then use "HAVING @counter % 120 = 0" to get the edges.

I'm simply stating that you shouldn't store data for two team in one record.

Are you asking how to set up replication?