fenway

And show EXPLAIN before and after.

You'll need to join the max timeslot back to the original table.

There's a strict mode option that prevents silent conversion of engine types -- use it.

You know, MySQL has collation conversions specifically to address this issue.

You can be extra fancy and initialize those variables as a 'join' to the inner query, too.

Not sure what you're asking -- client-side or server-side -- but in any event, it's not directly mysql related (since you obviously queried the table successfully to show the info in the first place).

Maybe syntactically you could convert them -- but that's akin to machine translation -- it's terrible.

Without the data, I'm guessing not all records have matching rows.

Since you don't want to automatically delete anything, you can easily effect what gets displayed by storing some version of the timestamp somewhere.

Well, for starters: SELECT SUBSTRING_INDEX( SUBSTRING_INDEX( post.alltags, ',', 1 ), ',', -1 ) AS tag1 ,SUBSTRING_INDEX( SUBSTRING_INDEX( post.alltags, ',', 2 ), ',', -1 ) AS tag2 ,SUBSTRING_INDEX( SUBSTRING_INDEX( post.alltags, ',', 3 ), ',', -1 ) AS tag3 FROM post

+1

Why all of the LIKE %%?

Everything is possible.

You can put your configuration file *anywhere* -- there's a known order for where to look, though.

http auth is a very quick-and-dirty solution -- but it's not flexible enough.

BIGINT UNSIGNED will get you what you want.

Well, it would require a number of self-joins and some fore-knowledge of the max number of values in the list.

What I think you mean to say is that GROUP BY and * is not working.

Well, you *do* recognize that issuing a query without examining the results will be 'nothing at all'.

Anything you 'feed' invalid e-mail addresses will just complain or log them -- so you can do the rest on input.

You can do all of this in MySQL with a JOIN and INSERT INTO .. SELECT WHERE.

Not explain, EXPLAIN.

Yeah -- do you really need to keep the state in the DB?

Yeah, FT is mysql is rather limited -- you'll have to mess with internals to trick it into using a hyphen a part of a word. I'd vote for Sphinx, too.

This is a mysql forum -- we don't *ever* need to see a JS function.