I'm using PHP 4.22, MySQL 3.23.53a on a RedHat Apache web
server.
I have a join that 99.9% of the time works fine but there have been
3 occasions in the last few weeks where extra records have found
their way into the resulting dataset. This has happened during high
load times.
The join is as follows:
select a.Username, b.MsgID, b.Subject, b.Body
from Users a, Messages b
where b.ForumID=$forumID
and b.ParentID=0
and a.UserID=b.UserID
order by $sortBy
limit $startRec,$endRec
On the 3 occasions that a problem occurred, records made their
way into the dataset that didn't have a b.ForumID equal to
$forumID. I've noticed a number of recent fixes listed for joins in
the MySQL doc and am wondering if something has slipped by.
Has anyone else seen this problem? Any ideas on how I could
avoid it? Would changing the form of my join help (i.e. do the join
in the FROM and not the WHERE clause with the JOIN keyword)?
Any suggestions would be greatly appreciated!
Regards,
Frank Tuvell
Atlanta, GA - USA
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
