4 messages in com.mysql.lists.clusterRe: JOIN with a ndbcluster engine| From | Sent On | Attachments |
|---|---|---|
| Klaus Berkling | 20 Jan 2005 07:59 | |
| Jonas Oreland | 20 Jan 2005 08:12 | |
| Johan Andersson | 20 Jan 2005 08:19 | |
| Klaus Berkling | 26 Jan 2005 11:11 |
| Subject: | Re: JOIN with a ndbcluster engine![]() |
|---|---|
| From: | Klaus Berkling (kber...@dyned.com) |
| Date: | 01/26/2005 11:11:56 AM |
| List: | com.mysql.lists.cluster |
Version 4.1.9 seems to have fixed this issue.
Thanks for the help.
On Jan 20, 2005, at 8:20 AM, Johan Andersson wrote:
Hi,
please upgrade to the latest version (mysql 4.1.9) and let us know if the problem persists.
B.r. johan andersson
Klaus Berkling wrote:
I am having an issue with a JOIN on two tables that are in a two node cluster.
What happens is that the columns in the joined table are all null.
students left outer join members on students.student_key = members.student_key
I should get something like this:
+----------------------+-----------------------+------------------- +---------------------+ | students.student_key | students.student_name | members.class_key | members.student_key | +----------------------+-----------------------+------------------- +---------------------+ | 5 | Grace | NULL | NULL | | 3 | Susie | NULL | NULL | | 1 | Bill | 3 | 1 | | 1 | Bill | 1 | 1 | | 4 | Jean | 3 | 4 | | 2 | John | 3 | 2 | | 2 | John | 2 | 2 | | 2 | John | 1 | 2 | +----------------------+-----------------------+------------------- +---------------------+
But I get something like this: +----------------------+-----------------------+------------------- +---------------------+ | students.student_key | students.student_name | members.class_key | members.student_key | +----------------------+-----------------------+------------------- +---------------------+ | 5 | Grace | NULL | NULL | | 3 | Susie | NULL | NULL | | 1 | Bill | NULL | NULL | | 1 | Bill | NULL | NULL | | 4 | Jean | NULL | NULL | | 2 | John | NULL | NULL | | 2 | John | NULL | NULL | | 2 | John | NULL | NULL | +----------------------+-----------------------+------------------- +---------------------+
These are not the real tables, the real tables are around 2000 rows
I don't have this problem on a much smaller scale (see above) or in a InnoDB database with 2000 rows. I only see the issue with an ndb cluster with 2000 rows, both tables are in the cluster. The columns are set to NOT NULL. I am using mysql 4.1.7.
Anyone seen this?
Thanks
kib
-- MySQL Cluster Mailing List For list archives: http://lists.mysql.com/cluster To unsubscribe: http://lists.mysql.com/cluster?unsub=kber...@dyned.com
kib
-- "What exactly is the function of a 'Rubber Duck'?" - Arthur Weasley
Klaus Berkling Systems Administrator DynEd International, Inc. <http://www.dyned.com/> (650) 375-7011 x125




