--- Sinisa Milivojevic <[EMAIL PROTECTED]> wrote: > Thank you for your bug report.
Anytime! :-) > Regarding inconsistent values returned for MERGE > tables, please refer > to our manual on how are UNIQUE values treated with > MERGE. I looked fairly thoroughly through the manual before posting. Which paragraph/section? I couldn't find anything that applies to compound keys. > Regarding a bug that crashes MySQL, this is a patch > that fixes it: With the patch installed, I get even stranger behaviour, on non MERGE tables: CREATE TABLE t1 ( a int(11) NOT NULL default '0', b int(11) NOT NULL default '0', PRIMARY KEY (a,b) ) TYPE=MyISAM; INSERT INTO t1 VALUES (1,1); INSERT INTO t1 VALUES (2,1); mysql> select max(b) from t1 where a = 2; +--------+ | max(b) | +--------+ | NULL | +--------+ 1 row in set (0.00 sec) WIthout the patch, the correct result '1' is returned. Thanks, Paul Ripke http://www.sold.com.au - SOLD.com.au - Find yourself a bargain! --------------------------------------------------------------------- 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
