fenway

IN() is just basically shorthand for a series of OR comparisons -- which explains why it doesn't work with NULL.

That's just poor data storage design -- there is no simple facility for handling this is the data are stored that way.

SELECT * FROM TABLE INNER JOIN TABLE AS TABLE2 ON ( TABLE2.id = TABLE.fid ) WHERE TABLE.id='$page' or TABLE.link_to_spouse='$page' or TABLE.fid= '$page' Of course, you'll need to decide which fields you want, and if there's always a non-NULL & matching fid or not. Also, don't use "table" as your table name.

There are some excellent sticky resources on storing hierarchical data -- but use LEFT JOIN instead of RIGHT JOIN, it's the more common variant.

Do you have backups/logs/etc?

No, you shouldn't -- but DISTINCT * is meaningless. In fact, don't ever use DISTINCT -- you'll thank me later.

Don't corrupt the raw data with an arbitrary number of zeroes.

The fid links back to the same table? Then self-join

You're talking about displaying results, not retrieving results -- that's php, not mysql.

This topic has been moved to PHP Coding Help. http://www.phpfreaks.com/forums/index.php?topic=306136.0

So only == 0 is different?

Then you'd need a left join.

That's not particularly efficient -- a cross join, one for each condition, would be preferable.

That's because you're using a left join -- you need it in the ON clause.

Yes, why not UNION?

maybe with mysql_error() you'd get some useful information.

This topic has been moved to PHP Coding Help. http://www.phpfreaks.com/forums/index.php?topic=305884.0

You'll have to sort the field into two parts -- not efficient at all -- but possible. EDIT: just missed the post post by 2 seconds.

I don't see your hoofdfoto restriction -- but you'll have to do this in two parts. Add that restriction to your where clause, and then if that's null, you'll have to get the "overall" max value.

Sync how?

That means your tmpdir is full.

Even more so, the actual length a given row.

They look like backticks.

Show us the EXPLAIN output.

Posting date is not possibly sufficient to relate a single question to a single answer -- try again.