fenway

You mean trigger into another table, or the same table?

Don't mix DISTINCT and GROUP BY -- that's misleading and error-prone. You can group by both columns.

Your table is just SCREAMING for a UID.

Have you started this project yet? If not, these three shouldn't be your primary concern.

Everything matters -- either it's the SQL statement (a string) or the query handle (an object).

Then you're not storing IPs correctly.

You really should always have a password for root.

Height as an ENUM field? Bad idea. Height as a VARCHAR? Bad idea.

Well, if I have the time, I'll either solve it again, or find the original post with the solution.

No need for subquery -- really, just a CROSS-JOIN for each attribute -- it's not a complex query.

You need to isolate a unique group first, and then join upwards.

Learning SQL is like learning English -- don't bite off more than you can chew.

You should NEVER need to retrieve the password.

Well, you're not supposed to store delimited data when you (a) aren't storing individual elements of an array and (b) need access to an arbitrary element. You're missing some tables. And SUBSTRING_INDEX() can help you if the want the "inside".

Oh, I really like that idea! +1

You need to cross join, once for each attribute.

Well, yes, if you self-join the table, and ensure increasing UID order with (> in the ON clause), you'll get tuples for each pairing of login times. But that's not very helpful. You could achieve some magic with user variables, though.

Yeah, but mixing DISTINCT, *,and GROUP BY is likely very bad.

Really?

You're mixing AND and OR -- probably not how you expect -- you're missing parentheses. IN() solves this nasty oversight. Also, assuming your 'deleted' column is rare, an index on that column might help too, since now EXPLAIN shows 'all' for the `xfiles` table.

Raw query as in non-active records? Sorry for the delayed response -- no, raw query as in the actual SQL statement being sen to the server.

Sorry about the delayed response -- I don't understand the question.

You don't have to log this in the DB -- but if you do so, just use INSERT DELAYED.

Again, post the EXPLAIN output.

I don't see a raw query.