fenway

Actually, that likely is the most efficient option, particuarly in earlier version of mysql.

Those are backticks.

You simply need to join these as derived tables.

Can you give an example of what doesn't work?

Well, you sort of have no choice -- you have to "check" if there has been another reply by someone else -- but you don't have to check it in real-time.

There is no "fixed" number -- it depends on the distribution of the data. The refman has more details.

Don't store phone number as integers.

Whoa... where's the JOIN condition? And don't you want a COUNT()?

You want LEFT JOIN... IS NULL.

What's wrong with null?

That doesn't make any sense for a unique index.

How do you mean?

Show us some sample output without all that group by stuff.

Does it not have something like that built-in? Otherwise, you simply need to issue a simply query and count the number of matching rows for a given team name -- if it's > 0, then you have a dupe.

This is referring to the decllaration of an SP...

I'm not sure I follow.

Then you need a new version of the mysql libraries.

Well, you need to establish what the rate-limiting step is -- are the mysql queries optimized? check EXPLAIN.

Well, debug the result set from your query directly -- otherwise, it's a php logic error.

I think you're mixing ORs and ANDs without parentheses...

Why not? There are ugly sql ways of doing this, but you'd need to tell us more about every possible variation in your dataset.

FTS acts funny on smaller datasts... how big is your table?

What you have seems correct... does it not work?

"Configured Max Per-thread Buffers" -- how is that being calculated? usually that's the worst-case scenario, so it's likely to be true.

If there's a timeout on the server side, you have to run your script in smaller steps.