db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manish Khettry" <manish.khet...@gmail.com>
Subject Re: DERBY-581 and OLAP operations
Date Wed, 18 Jul 2007 21:18:57 GMT

It sounds like a very reasonable and thoughtful way to get started. One
thing which is frustrating about working with Derby is that large portions
of the code are so very cryptic and brittle, sometimes unnceccsarily so.
Having more than one person try and understand relevant code, documenting it
and sharing this information would help in more ways than one.

The other thing-- is it possible to get a hold of the relevant portions of
the SQL standard that you refer to?


On 7/18/07, Bryan Pendleton <bpendleton@amberpoint.com> wrote:
> In the context of https://issues.apache.org/jira/browse/DERBY-581
> I've been studying the SQL-99 standard's specification of
> OLAP operations:
>   - Feature T611 specifies "Elementary OLAP operations"
>   - Feature T612 specifies "Advanced OLAP operations"
> I'm interested in exploring an implementation of these features,
> and to start with I'd like to get the community's reaction:
>   - Are these features that we're interested in seeing added to Derby?
>   - Are there others in the community who are interested in
>     working on these features?
>   - How could we approach this incrementally, building enough
>     functionality to be useful, arriving at a complete
>     implementation in pieces over time? For example, would it be
>     reasonable to build a subset of the T611 features at first,
>     and then expand that functionality over time? Would it be
>     reasonable to add new SQL syntax support, but have it work
>     only in a subset of cases, and then expand the execution
>     functionality over time to address more usages?
> I was thinking that I might get started by trying to build
> one or more Wiki pages that describe some of the materials
> that might go into an implementation:
>   - background information about the features and the
>     concepts behind them
>   - notes about the current Derby implementation, and about
>     possible ways to extend the implementation in this area
>   - ideas for how to subdivide and stage the implementation,
>     in order to enable us to start talking about actual code.
> Does this seem like a reasonable approach?
> thanks,
> bryan

View raw message