fenway

What was the issue?

You should be building your WHERE clause dynamically.

This is a continuation of this thread... no need to start a new one next time. This is a VERY BAD idea... you don't need 10,000 tables for 10,000 users.

hard to believe....

So what is your point? It's better to use the COUNT function in the query rather than mysql_num_rows() function of PHP? YES -- that's exactly my point... if you only want the actual value of the count.

You need a LEFT JOIN... IS NULL.

Let's see it.

Then you want: SELECT a.* FROM RQquestions AS q LEFT JOIN RQanswered AS a ON ( q.ID = a.qID ) WHERE a.qID IS NULL ORDER BY RAND() LIMIT 1

Yes... use FIND_IN_SET().

MySQL will tell you if the syntax is correct...

No paren around the default value...

Did you try count(arcade_games.champion)?

Seems like rules 1 & 2 are the same...

As long as you're ordering by the non-joined table, the order should remain the same.

Define "not work"... no results, error, etc.?

Depends on the query and the data... more info please?

But you can using it a HAVING clause... and sometimes you can.

Like paul said, as long as these tables should really exist separately, you're probably ok

Why? What is the performance difference between mysql_num_rows and using COUNT in the query? If you query matches 10,000 rows, why send all 10,000 rows from the server to the client, create a PHP object, and then have to count them, when you can simply return a single number?

Depends... you could have this as another line item in the computers table.

Sounds like you want a left join... but why the limit?

So you have all of the lines, categories, parts, etc. in a single table?

You probably want AND f.member_id IN ( instead of AND f.member_id = (

It's not more work -- go back to modify your original query; for example: SELECT SUM(IF(DAmodeo='1',1,0)) AS DAmodeoCNT, SUM(IF(KArgyros='1',1,0)) AS KArgyrosCNT FROM DB_VOTES Obviously, you'll need to refer to the appropriate aliases in your php code, too.

It's useful to separate data vertically if there are TEXT/BLOB fields that are rarely used, or the main table is read often, updated rarely... this will improve query cache performance.