John Heitmann writes:
> Hello,
>
> I have come across a possible bug in MySQL that causes NULL values to
> be erroneously returned from a join.
>
> Problem: An inner join between two tables succeeds, but one column is
> erroneously returned as all NULL if the join occurs after a delete in
> table 1.
>
> Platforms Tested: 3.23.43 (Solaris, Linux, Mac OS X), 3.23.47 (Linux)
>
> Detail:
>
> I have attached a stripped down version of the problem tables. Perform
> the following actions after loading the tables:
>
> select t1.*, t2.name from t1, t2 where t2.id=t2_id;
> Note that the column 'item_id' returns the expected answers.
>
> delete from t1 where t1_id=97;
> select t1.*, t2.name from t1, t2 where t2.id=t2_id;
> Note that the column 'item_id' is now unexpectedly all NULL.
Hi!
The above is actually expected behaviour, as you are not doing a join
at all, but a full Cartesian product.
--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <[EMAIL PROTECTED]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com
---------------------------------------------------------------------
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
