Strange behaviour of MySQL-3.23.51

I have a database structure as follows (simplyfied) : CREATE TABLE masterTABLE ( pid int(11) unsigned NOT NULL default '0', c1id int(11) unsigned default NULL, c2id int(11) unsigned default NULL, value int(11) unsigned NOT NULL default '0', UNIQUE KEY pid2 (pid,c1id,c2id), UNIQUE KEY

AW: Strange behavior of MySQL 3.23.51

And what about the WHERE-Clause?? It is not used in Statements with Aggregat functions? ... cool answer ... but I really can't think so ... > -Ursprüngliche Nachricht- > Von: Mikhail Entaltsev [mailto:mike_lynx@;smtp.ru] > Gesendet: Montag, 21. Oktober 2002 18:42 > An: [EMAIL PROTECTED];