select distinct - order by - limit 2 results in one single result #3527
Last updated: 2014-10-31 14:14:41 +0100
Date: 2014-08-06 14:31:20 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.58 Safari/537.36
I was unable to make a small example, thus I have exported the column that was causing this. A table with a lot of distinct entries results in one single result (after ordering) while many are expected.
Steps to Reproduce:
Load the table, will be attached. Execute:
select distinct userstopcode from "sys"."test_userstopcode" order by userstopcode asc limit 2;
sql>select distinct userstopcode from "sys"."test_userstopcode" order by userstopcode asc limit 2;
sql>select userstopcode from "sys"."test_userstopcode" group by userstopcode limit 2;
MonetDB 5 server v11.17.22 (64-bit, 64-bit oids)
Date: 2014-08-06 18:41:13 +0200
which version did you test on. I just run a simple test like this on both
Date: 2014-08-06 20:07:17 +0200
My simple tests do not fail either. Thats why I e-mailed the table dump. Currently at Jan2014.
Date: 2014-08-07 09:58:43 +0200
the current implementation(s) of firstn and pqueue topn seems to handle multi column topn/firstn okay, but distinct needs a small adjustment. The one but last
Date: 2014-08-07 10:45:47 +0200
I wondered while making the example for this bug. Why isn't it reproducable with a table with 3 rows?
Date: 2014-08-13 11:18:21 +0200
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d380de461d7a
Date: 2014-08-13 11:25:25 +0200
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b373303ee299
Date: 2014-08-13 19:54:44 +0200
fix is in Oct2014 branch
Date: 2014-10-31 14:14:41 +0100
Oct2014 has been released.
The text was updated successfully, but these errors were encountered: