Best wishes, of course!
I'd replied to this thread, wondering if there is a way to specify the
library in the connection string. Turns out there is the "libraries"
property that can be specified - if using the native JDBC driver, it
takes only the first in a comma-separated list. If the JT400 driver, it
will add all the libraries one specifies to the library list - not sure
if there's anything related to naming, which is another property.
So this can be used for probably any RDBMS - the connection properties
will likely be different but they probably do whatever is needed for
On 2/4/2013 5:26 PM, Scott Klement wrote:
Yes, this is true. I would point out, however, that you have the
source code for JDBCR4 and could add this easily.
There are probably a million things like this -- useful features that
could be added to stuff like JDBCR4. When I get a great tip like this
one from Dan Kimmel, I will try to add them... But, it may be awhile
due to my current medical condition.
If you can think of any other things you'd like to have in JDBCR4,
please send them to me, and I'll keep a list.
On 2/4/2013 4:44 PM, James H. H. Lampert wrote:
On 2/4/13 10:34 AM, Dan Kimmel wrote:
JDBC abstracts away this kind of difference between underlyingExcept that as of yet, JDBCR4 doesn't appear to have an RPG-callable
databases. Use (Connection)con.setSchema(String schemaName) rather
than trying to work out which database engine you are using. Don't
use the "SET SCHEMA" or "USE " statements. Let the driver work out
what is the appropriate statement.
front-end for setSchema. At least, not that I can see in a DSPSRVPGM or
in the source member.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact