Date comparison returns incorrect results #3834
Last updated: 2015-11-03 10:18:28 +0100
Date: 2015-10-23 17:54:24 +0200
Run the following queries, and observe that the SELECT query returns empty result, while the tuple with "mydate" value '2012-03-09' does satisfy the WHERE condition:
CREATE TABLE datepoint (mydate DATE, insiderange BOOLEAN DEFAULT FALSE, rangename CHAR(8));
This problem seems rather specific with the number of tuples inserted into "datepoint", OR the order in which they are inserted.
The only difference in the following queries is that one more tuple is inserted into "datepoint", then the SELECT query returns correct results:
The only difference in the following queries (compared with the first set) is that the tuples are inserted in the reverse order, then again the SELECT query returns correct results:
Date: 2015-10-23 18:10:14 +0200
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=91007a50e91b
Date: 2015-10-23 18:16:15 +0200
The strange thing is, when running the query with Mtest.py, the first SELECT query does return correct results. While the problem occurs with just "mclient date_comparison_incorrect_results.Bug-3834.sql" ...
Date: 2015-10-25 00:11:23 +0200
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=565c496e66c0
Date: 2015-10-25 00:12:02 +0200
fixed. The reverse sorted case is now properly handled in the rangejoin code.
Date: 2015-10-27 15:06:10 +0100
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=54e21e04d706
Date: 2015-11-03 10:18:28 +0100
Jul2015 SP1 has been released.
The text was updated successfully, but these errors were encountered: