Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

quantile(col, 0) and quantile(col, 1) fail #3773

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

quantile(col, 0) and quantile(col, 1) fail #3773

monetdb-team opened this issue Nov 30, 2020 · 0 comments

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2015-07-21 10:12:41 +0200
From: @sjoerdmullender
To: SQL devs <>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes

Last updated: 2015-08-28 13:42:13 +0200

Comment 21030

Date: 2015-07-21 10:12:41 +0200
From: @sjoerdmullender

compare the two plan:

create table x (y decimal(10,4));
plan quantile(y, 0.0) from x;
plan quantile(y, 0) from x;

The first works, the second doesn't. However both are questionable.
The first casts column y to double (why?), the second casts it to tinyint(!).

I think there should be no cast at all of column y, since quantiles are defined on all integer types (there may have to be some higher level magic to deal with decimals).

Comment 21037

Date: 2015-07-22 10:08:30 +0200
From: @njnes

improved aggregation function resolution.

Comment 21038

Date: 2015-07-22 10:20:37 +0200
From: MonetDB Mercurial Repository <>

Changeset b26c48634f0d made by Niels Nes niels@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b26c48634f0d

Changeset description:

added tests for bugs 3775 and 3773

Comment 21040

Date: 2015-07-22 10:23:29 +0200
From: MonetDB Mercurial Repository <>

Changeset 7bd0dd798226 made by Niels Nes niels@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7bd0dd798226

Changeset description:

when we cannot resolve a aggregation function on all types, fallback to
searching based on name, number of arguments and first argument type.
Solve bug #3773

Comment 21206

Date: 2015-08-28 13:42:13 +0200
From: @sjoerdmullender

Jul2015 has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant