Guess the shirt answer is: no-one thought of / implemented it so far.
We'll see what we can do when.

Stefan

On July 21, 2015 2:56:03 AM CEST, Anthony Damico <ajdamico@gmail.com> wrote:
hi team, any chance you could give this a look before the next release candidate?  i'm confused why QUANTILEs of 0 and 1 don't go straight to MIN and MAX..  thanks!

On Mon, Jul 13, 2015 at 8:24 PM, Anthony Damico <ajdamico@gmail.com> wrote:
hi monetdb team, i am getting errors below on data i can't share.  before i spend a bunch of time trying to create a reproducible example for this:

i've confirmed that MIN and MAX both do work on this column, and also that QUANTILE works with 0.01 thru 0.99 on this column.  is there a reason QUANTILEs of 0 and 1 don't simply call MIN and MAX?  thanks!


Error in .local(conn, statement, ...) :
  Unable to execute statement 'SELECT QUANTILE( tot_pay , 0 ) FROM acons WHERE yr = 2013 AND ( dattyp1 = 1 OR dattyp2 = 1 OR dattyp...'.
Server says 'overflow in conversion of 43553.818965373482 to bte.' [#22003].
>
> unwtd_pct <- dbGetQuery( db , paste( "SELECT QUANTILE( tot_pay , 1 ) FROM acons" , where_clause ) )
Error in .local(conn, statement, ...) :
  Unable to execute statement 'SELECT QUANTILE( tot_pay , 1 ) FROM acons WHERE yr = 2013 AND ( dattyp1 = 1 OR dattyp2 = 1 OR dattyp...'.
Server says 'overflow in conversion of 43553.818965373482 to bte.' [#22003].
>



users-list mailing list
users-list@monetdb.org
https://www.monetdb.org/mailman/listinfo/users-list

--
| Stefan.Manegold@CWI.nl | DB Architectures (DA) |
| www.CWI.nl/~manegold/ | Science Park 123 (L321) |
| +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |