>think you can give your problem another approach, splitting it in two
>queries and joining the result sets through php script.
>Sometimes you can't put SQL to do all the work.
That's true, but in most cases it is more efficient to leave the joins,
orders etc. in the DB, because its more optimzed for such dumb processes ...
mk
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
