fenway

Debugging SPs is annoying -- but insert into a dummy log table at every step of the way, and you'll see what's going wrong.

I don't see a hierarchy anywhere.

The only way I've ever handled this is with user variables -- store the last score, and a related counter. Increment the counter each time the score is the same, otherwise, reset both.

And next time you post entire scripts -- let alone outside code tags -- I'll lock the thread.

You can't use GROUP BY that way --

You can have a unique index constraint across multiple columns.

Yes -- one query at a time. Seriously.

Don't even consider doing this -- this is a horrible, horrible idea.

Drop the parens around your select column list.

Never post the entire code. And this isn't a mysql problem.

I don't see what happens when you click submit -- but that's not a mysql question anymore.

You're looking for LAST_INSERT_ID().

Yeah, you can use * with LIKE, but it's slow. Yes, if you store min/max, you can use BETWEEN. As for keywords, there are different options -- if it's not crazy large a simple EAV table will suffice.

What alter statement are you talking about?

You'll need user variables.

Chunk the records.

What?

You need a group by

That's not english.

Is this a new problem?

Say what?

Huh?

Sorry, I don't follow.

To clarify, I don't know what's even parsing that xml, or how it's being handled.

Not that it would be particular efficient, but you could strip out the numeric part dynamically and then sort of the remaining string as a secondary ordering clause.