fenway

Well, your table isn't normalized... but regardless, you'll have to determine which fields to search based on the criteria provided, and optimize accordingly.

Agreed.

As you've discovered, multi-valued inserts will only return the first auto-increment value -- that's for replication -- but if you need the actual IDs for each one, you'll have to run each separately.

So you're questioning the 2NF?

That's quick strange... even after ANALYZE?

I'm assuming Monday is long gone -- though we do have a strict "homework" policy. However, if you still can't figure something out, feel free to ask.

Huh? What's the mysql question here?

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

You can use instead.

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.

MySQL doesn't have built-in functions for that.