Re: Restricting a Data Source in BIRT

I have been using connection strings like:

jdbc:as400://10.0.10.205;libraries=Lib1 LIB2 LIB3;naming=system;

and those are the libraries used by the connection. Perhaps that approach will work for you?

Pete Helgren
Value Added Software, Inc
www.asaap.com
www.opensource4i.com


On 4/18/2011 10:39 AM, James Lampert wrote:

We are currently experimenting with BIRT, accessing DB2/400 data.

When we set up a Data Source with a URL of jdbc:as400://foo.bar.com (the
name has been changed to protect the innocent), we connect just fine,
but when we go to create a new Data Set, we end up with a list of the
first 20 libraries in alphabetical order, NOT including the library we want.

But we can select the desired library (we'll call it WTFOOBAR here) from
the Schema drop-down.

Ideally, we don't really *want* end-users to be kicked into this situation.

We tried changing the URL in the Data Source to
jdbc:as400://foo.bar.com/WTFOOBAR
and nothing about its behavior changed.

We tried changing it to
jdbc:as400://foo.bar.com:currentSchema=WTFOOBAR
and again, nothing about its behavior changed.

Anybody know what we're doing wrong here?

--
JHHL