[ 
https://issues.apache.org/jira/browse/DERBY-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Lewis updated DERBY-5466:
-------------------------------
    Attachment: DERBY.5466.aggtest.patch

Here is a patch that creates test methods for the var_pop and stddev_pop 
functions.  I patterned these after the avg functions, modified the data and 
test comparison values.   These two tests pass.  Before I go onto create 
var_samp and stddev_samp I would like to make sure this is going to be 
suitable, so that's why I'm attaching this before complete.

> Add support for SQL Standard statistics functions, such as STDDEV_POP, 
> STDDEV_SAMP, VAR_POP, VAR_SAMP
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5466
>                 URL: https://issues.apache.org/jira/browse/DERBY-5466
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.8.1.2
>            Reporter: Lukas Eder
>            Priority: Minor
>              Labels: derby_triage10_10
>         Attachments: DERBY-5466.stats.patch, DERBY.5466.aggtest.patch, 
> derby-5466-01-aa-aggregatorClasses.diff, derby-5466-02-aa-bindLogic.diff, 
> derby-5466-02-ab-bindLogic.diff, derby-5466-03-aa-distinctError.diff, 
> var_pop_formulas.txt
>
>
> Any of these RDBMS support the SQL standard statistics functions STDDEV_POP, 
> STDDEV_SAMP, VAR_POP, VAR_SAMP:
> - DB2 (only STDDEV, VARIANE)
> - H2 
> - HSQLDB 
> - Ingres 
> - MySQL 
> - Oracle 
> - Postgres 
> - SQL Server (named STDEVP, STDEV, VARP, VAR)
> - Sybase ASE
> - Sybase SQL Anywhere
> These don't:
> - Derby
> - SQLite
> This would be a useful addition for Derby, I think.
> An even larger example list of possible statistics aggregate functions is 
> listed in the Postgres documentation:
> http://www.postgresql.org/docs/9.0/static/functions-aggregate.html#FUNCTIONS-AGGREGATE-STATISTICS-TABLE



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to