fenway

You can't use an aggregate expression in the WHERE clause -- move it to HAVING.

Sounds like you could just UNION the appropriate tables.

When you say "row number", do you mean the auto-increment column? It won't get re-used unless you truncated the table.

Not "parents", parens -- parentheses. You can't mix ANDs and ORs that way, since they have the same precedence -- you need to group all of the ORs together.

Yes, you need to JOIN the tables -- the speed will be depending on the indexes you choose and your version of mysql. Easiest way to handle this is simply to UNION the various options: ( select * from table2 inner join table1 on ( table1.column1 = table2.column1 ) where table1.status = 1 ) UNION DISTINCT ( select * from table2 inner join table1 on ( table1.column1 = table2.column2 ) where table1.status = 1 ) UNION DISTINCT ( select * from table2 inner join table1 on ( table1.column2 = table2.column1 ) where table1.status = 1 ) UNION DISTINCT ( select * from table2 inner join table1 on ( table1.column2 = table2.column2 ) where table1.status = 1 ) Of course, this makes me question your design.

Huh?

Define "working".

TLDR... what's wrong with that query?

Actually, that's precisely what I suggested.

You're missing parens.

There is no "update from".

Change the default for that column with ALTER.

Then don't add them to the query -- don't blame mysql for executing a query that you type.

I'd hope there was an ODBC interface.

What's that a log of?

I see no reason why not, as long as it's not recursive.

Not a chance that anyone but you can read through that.

Moving it to the DB should be the last step, if at all.

Sorry, I don't follow.

Yikes. Why not Availability.*?

So it's not using any indexes, eh?

The lazy way is to use a bunch of ORs, and check a count in the having clause. I prefer to cross join the table to itself, one for each condition.

According to me, yes.

Why would you even want to?

Basically, it depends on what's causing the error -- if you're getting php errors, it's not mysql's fault.