fenway

Sorry, I thought you had names spanning fields, not the reverse. You can't pass the "total name" and make it work. You'll have to search each field.

How is a total over 1000 complicated for a machine?

You could store minutes.

Yup... add a new DATE column, convert using STR_TO_DATE(), then drop the old one, and then mysql date math is a joke.

Ignoring for the time being that this is likely a poor storage choice, you can build this pseudo-structure in advance, and then just interpolate a simple string. But that's a php syntax question.

If you're talking about including HTML in a field, this has nothing to do with either php or mysql... just dump out the contents as-is (assuming you're not messing around with entities and such). Otherwise, if you want to link the entire record to something, you'll need another field. And no, phpmyadmin doesn't know anything about either of these.

Yes, you'll need to run "SELECT LAST_INSERT_ID()" afterwards, but not a true mysql query.

And what's wrong? Other than a poor choice for a title?

If the file is a reasonable size, you can extract the field in a text editor -- otherwise, sed and grep are your friends.

Sounds like you need to clean up your database.

Not really... now you've posted (1) a query that won't work with multiple keywords and (2) a query that's not valid at all. My comment referred to your original query, mixing ANDs and ORs without parentheses.

Oh, it is VERY necessary -- don't kid yourself.

LIKE won't return anything useful... you'll have to count either in mysql or application code.

Read the refman on LAST_INSERT_ID() with with a parameter -- very cool, mostly unknown functionality, explicitly for this purpose.

Well, if you want that history, you have to store it somewhere.

Define "most".

Like I said earlier, just dupe the record.

But this kind of thing should never be done in the query itself. Get the value, get the count, and have the script output them as you please.

hard to graph text, but sure. You simply need to duplicate your records instead of overwriting them.

Persistent connections are evil... open/close once per script, and don't write poor queries that take a long time to execute. Bandwidth for most queries is not an issue.

You don't have parens where you should have them.

FULLTEXT will ignore most of these characters, but comes with it's own issues.

Why?

Well, that version of mysql can only use one index per query, so having "lots of indexes" won't help. Besides, no matter what you do, skipping ~17000 rows just to show 20 is crazy slow -- ALWAYS.

Actually, you can write it this way: SELECT @rank := @rank +1 AS rank, userid, percent FROM ranking, ( SELECT @rank := 0 ) t1 ORDER BY percent DESC And not have to worry about it.