Re: [Olap4j-devel] Some API changes before 1.0

[Luc B. <luc...@gm...>]

I disagree with your point #2, and I have a very realistic scenario to
demonstrate why. Let's say you are building an OLAP client. Your application
maintains a minimal pool of connections and emits an OlapPreparedStatement
when some parts of it want to execute a query. This is a very common
development pattern that prevents an application from hosing a server.

Now, what happens if another part of the application explores the
connection's metadata. It would have to access the connection, change the
current database value for each that are available, thus impacting all other
statements that are used elsewhere.

This example demonstrates perfectly why a database metadata object should
not be dependent on the connection settings, but should rather expose
entirely what is available, in respect to the credentials.

_____________________________
Luc Boudreau


On Thu, Jul 1, 2010 at 4:26 PM, Julian Hyde <jh...@pe...> wrote:

>  I just discovered
> http://sourceforge.net/tracker/?func=detail&aid=2115057&group_id=168953&atid=848537.
> It seems to solve some of the major issues with this proposal, viz:
>
> 1. What XMLA calls 'data source' will in olap4j be called 'database'. This
> prevents confusion with javax.sql.DataSource.
>
> 2. A connection will have a 'current database'. That means that we will not
> need to add a 'String database' parameter to the OlapDatabaseMetaData.getXxx
> methods.
>
> Julian
>
>  ------------------------------
> *From:* Julian Hyde [mailto:jh...@pe...]
> *Sent:* Thursday, July 01, 2010 1:20 PM
> *To:* 'Luc Boudreau'; 'ola...@li...'
> *Subject:* RE: [Olap4j-devel] Some API changes before 1.0
>
>  JDBC has a two level namespace (catalog + schema). Can you remind me why
> we decided to extend this to three levels with data source?
>
> In moving to three levels all of the getXxx methods in OlapDatabaseMeta
> (and those inherited from DatabaseMetaData, some of which are relevant to
> OLAP servers) would require an extra parameter. That's not something I would
> do lightly.
>
> Julian
>
>  ------------------------------
> *From:* Luc Boudreau [mailto:luc...@gm...]
> *Sent:* Thursday, July 01, 2010 1:06 PM
> *To:* ola...@li...
> *Subject:* Re: [Olap4j-devel] Some API changes before 1.0
>
>
> I also just realized that the OlapDatabaseMetaData has many discovery
> related methods that don't allow arbitrary Datasource names.
>
> ie.
>  ResultSet getMeasures(
>         String catalog,
>         String schemaPattern,
>         String cubeNamePattern,
>         String measureNamePattern,
>         String measureUniqueName) throws OlapException;
>
> Was that intended or is this something we should fix while we're at it?
>
> _____________________________
> Luc Boudreau
>
>
> On Thu, Jul 1, 2010 at 3:23 PM, Luc Boudreau <luc...@gm...>wrote:
>
>> Hello everyone,
>>
>> I'd like to initiate the final push towards 1.0 and propose the following
>> changes to the API. I created a Google Document for us to work on. By
>> default, everyone has read access. If you want to have write access, send me
>> an email and I'll give you the proper access rights.
>>
>>
>> https://docs.google.com/document/edit?id=1P8yIF8MpaseDYnPga1nY3VEaM0POUo4imkiD-7kIoPA&hl=en&authkey=COCdsJoO
>>
>> So far I've listed all the changes I'd like to make to the OlapConnection
>> interface. We have a dire need to standardize this in order to respect the
>> functional specifications that were established a while ago. I'm expecting
>> feedback on this during next week. I'd like to make the changes the week
>> after.
>>
>> There will obviously be more changes required, but let's start with those.
>>
>> Luc
>>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> olap4j-devel mailing list
> ola...@li...
> https://lists.sourceforge.net/lists/listinfo/olap4j-devel
>
>