fenway

Post the output of the first query... and what you'd like the second query to display.

Try "SELECT title, replace(Title,'#','') as NewTitle FROM content ORDER BY ID DESC LIMIT 150" and see what happens.

But it sounds like you're _using_ innodb tables?

Title, full, then first 4 chars of type.

Yes, but it's not being used for the order by clause... and you have two indexes called date alias/

There's an AVG() function... but you need to join these queries.

Well, issue the equivalent select and make sure everything's as expected.

Why was innodb not available?

Try "ORDER BY (IF countryid = <the-id-of-the-US>, 0, 1), country_name ASC"

You're ordering by two columns, you only have one in your index.

Forgot about all those other joins for a minute.... including the ones in your dervied table. You already have the min/group by for the singles by breed; then just join this table to singles table using breedid and besttime, and THEN join the rest in.

Why not the check the error log first?

You won't be able to do this on a remote server unless it's configured to do so...

Where's the ON clause?

Yes, echo can't do "nothing".

But you shouldn't use the ID -- you have a date field!!!!!

Then you should simply have the two-column index instead.

I don't know what you mean... skip-networking does just that, effectively.

3 times? No! Use a third many-to-many table as suggested.

I don't like the fact that you're referring to #1 as UID 1 -- don't change UIDs *ever*. Order the results by something else.

Using anything other than the ID for sorting records is preferred... using LIMIT without an ORDER BY clause can produce unexpected results.

It's surprisingly difficult to compare rows to each other... this falls far outside the scope of the "set" that almost all RDBMS are based upon. You'd need a join for *each* row! That is, it needs to be interative... so unless you're going to use an SP, you're stuck.

That doesn't look like the error log file, that looks like a screenshot of the running process. And what's wrong with innodb?

Provided you can use an order by clause, you can LIMIT 150.

What does the error log show?