fenway

This topic has been moved to Installation & Configuration Issues. http://www.phpfreaks.com/forums/index.php?topic=344833.0

OF course, you're missing DB normalization entirely.

Hard to see join conditions with theta syntax.

Someone catch me up.

It will help *me*.

You shouldn't be running one query per day.

MySQL will only use an index from the first joined table for ordering

Echo the queries.

Yes, but depending how you're handing injection vectors, the quotes rarely hurt.

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

Depending on the size of the actual tables, that might no be so much.

How's that any different?

And where, exactly, are you seeing evidence of this fragmentation?

I mean the post that appears on the first page of the MySQL Help forum -- called the MySQL stickly.

That's what INSERT... ON DUPLICATE KEY UPDATE... is for.

I mean your connection script can choose 1 of the 10 possible users in a predictable fashion that switches for each new visitor to your site.

Did you run OPTIMIZE TABLE as the tuner suggests?

This topic has been moved to PHP Regex. http://www.phpfreaks.com/forums/index.php?topic=344564.0

My comment still applies.

If you sort by an expression, you're going to get a filesort --- nothing you can do about that at the moment. But yes, if you sort by "ORDER BY IF( done = 0, 1, -1 ) DESC, posted DESC", you'll effectively get what you want.

You mean HAVING, not WHERE -- you can't use aliases in the WHERE clause, they don't exist yet.

ORDER BY FIELD(....).

You're not supposed to have that boolean value -- you're supposed to join the tables.

have you tried --- reading the sticky?

I have no idea what you're talking about, probably because your DB design is very confusing -- you have a table and field named the same thing.