fenway

There's no "other trip"... same query.

LAST_INSERT_ID().... and php mysqli library has a function for this too.

The LEFT JOIN vs INNER JOIN is going to be signficiant here.

I can't see this ending well.

I think I must have brain fade as I cannot see how at the moment and I would prefer to avoid using HAVING. All the best Keith No, my turn for brain fade.... I didn't read the OP's question closely enough.

"table upgrade required" is rarely from corruption.

Not really the wrong place... though at some level it might be considered app design, depending on whom you ask.

Make sure your expression for substring_idnex() actually returns what you expect.

I don't follow.

So, where do we stand?

What's wrong with it now

Why? It's a joke in mysql -- NOW() + INTERVAL 24 HOUR.

Please tell us that you have managed to come up with a bit more detail.

You have e-mail in single quotes, not backticks.

So, solved?

I'm just suggesting that at the row level you need to have some record say "user X is friends with user Y".

Upgrade???? What changed?

More likely it's better to either (a) have a single row per language or (b) have a single table per language.

Even better would be (a) not to use plaintext passcodes and (b) not the pass them at all to the query.

Yikes... where's the join condition.

Agreed... it's just more overhead for no reason.

Normal forms are evil and complicated to explain. If any information is duplicated across rows or columns, then it's not normal enough -- start with that.

You need to get the first round of averages, place those in a derived table, then average again.

You can do something similar with MAX() without incurring any HAVING performance penalties.

Um, where's the connection?