Bug #13165 | select error... | ||
---|---|---|---|
Submitted: | 14 Sep 2005 6:41 | Modified: | 14 Sep 2005 10:51 |
Reporter: | SeungJun Lee | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 5.0.12-beta | OS: | Linux (fedora core 2) |
Assigned to: | CPU Architecture: | Any |
[14 Sep 2005 6:41]
SeungJun Lee
[14 Sep 2005 6:43]
SeungJun Lee
Hi... I have select error in my mysql cluster system...(ver. 5.0.12-beta) My system is... 1 mgm node 2 sql node 4 data node Error is.. When I run "select" in sql node, first, mysql> select b_index from tbl_myboard where myzean_code = '4' and category_code='27'; +---------+ | b_index | +---------+ | 54 | | 30 | | 33 | | 53 | | 57 | | 58 | +---------+ 6 rows in set (0.09 sec) second, mysql> select b_index from tbl_myboard where myzean_code = '4' and category_code='27'; +---------+ | b_index | +---------+ | 53 | | 57 | | 58 | +---------+ 3 rows in set (0.09 sec) third, mysql> select b_index from tbl_myboard where myzean_code = '4' and category_code='27'; +---------+ | b_index | +---------+ | 54 | | 30 | | 33 | | 58 | | 53 | | 57 | +---------+ 6 rows in set (0.09 sec) fourth, mysql> select b_index from tbl_myboard where myzean_code = '4' and category_code='27'; +---------+ | b_index | +---------+ | 58 | +---------+ 1 row in set (0.09 sec) fifth, mysql> select b_index from tbl_myboard where myzean_code = '4' and category_code='27'; +---------+ | b_index | +---------+ | 54 | | 30 | | 33 | | 58 | | 53 | | 57 | +---------+ 6 rows in set (0.09 sec) correct result is... mysql> select b_index from tbl_myboard where myzean_code = '4' and category_code='27'; +---------+ | b_index | +---------+ | 54 | | 30 | | 33 | | 58 | | 53 | | 57 | +---------+ 6 rows in set (0.09 sec) How can I solve this problem...?
[14 Sep 2005 10:51]
Hartmut Holzgraefe
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. Thank you for your interest in MySQL.
[14 Sep 2005 11:02]
Hartmut Holzgraefe
Bug #13170 is actually the duplicate, closed this one as 13170 has more info