5 messages in com.mysql.lists.win32Re[2]: Have I found a CRITICAL BUG in...
FromSent OnAttachments
CRO...@bouyguestelecom.fr14 Apr 2004 11:03 
Armando14 Apr 2004 16:31 
CRO...@bouyguestelecom.fr15 Apr 2004 02:23 
Andrey15 Apr 2004 02:45 
Armando15 Apr 2004 09:16 
Subject:Re[2]: Have I found a CRITICAL BUG in MySQL 4.1.1a-alpha-nt ???
From:Andrey (and@itime.ru)
Date:04/15/2004 02:45:21 AM
List:com.mysql.lists.win32

Hello CROCHE,

Thursday, April 15, 2004, 3:23:49 PM, you wrote:

Cbf> SELECT block FROM test WHERE idate BETWEEN '2004-01-01' AND '2004-02-15'
AND Cbf> country = 'GBRF'; Cbf> -> 1000 rows ( by the way how can I remove this 1000 limit with mysqlcc ?)

Cbf> SELECT block FROM test WHERE idate BETWEEN '2004-01-01' AND '2004-02-15'
AND Cbf> country = 'GBRF' GROUP BY block; Cbf> -> empty set Sorry, Christian, but I can't repeat your bug.

create table test ( idate date, block varchar(15), country varchar(15), minutes
float ); insert into test values ('2004-01-10','44011','GBRF',0),('2004-01-12','44013','GBRF',0), ('2004-02-15','49016','DEUF',0),('2004-02-17','49061','DEUF',0); select ...

returns me correct results. I ran it in: 3.23.53, 4.1.1a, 4.1.2 (2004.2.18 build).

Cbf> This really looks bad. I find it difficult to believe that such a bug would Cbf> not have been detected before. Does anyone has a clue here? Can somebody Cbf> maybe check this pb under Unix ? (I can sent the tables & data if needed) Send me dump of your tables (mysqldump -Q DB table > file.sql) and your INI file (or only [mysqld] section).