|
Thanks, Richard. That makes sense. You shouldn't need the toolbox to access data via JDBC. JDBC drivers are shipped with the database, similar to the way that the JVM is shipped with the operating system. The only difference is that in this case, the database and the OS are integrated. And please, folks, don't get the idea that I'm 100% against JDBC, my original inflammatory statement to the contrary <grin>. I've come to the conclusion that there are applications where SQL (and by extension JDBC) can be very effective. And there are some where, frankly, JDBC is the required regardless of performance issues (for instance, if you're accessing a non-DB2 database). It seems to me that there are entire classes of business transactions where SQL is probably better suited than native I/O. Month-end and year-end file updates come immediately to mind. For any sort of set-based processing - that is, business problems that are naturally suited for set-based processing, not applying set-based processing to traditional business problems - SQL should be considered. But even so, the SQL should always be encapsulated, either in server programs on the host or in data source classes. If you have naked SQL statements in your application mainline, this is begging for trouble. Joe Pluta www.plutabrothers.com > -----Original Message----- > From: java400-l-admin@midrange.com > [mailto:java400-l-admin@midrange.com]On Behalf Of Richard Dettinger > Sent: Tuesday, October 16, 2001 10:34 AM > To: java400-l@midrange.com > Subject: RE: Data access across libraries > > > > Sorry to jump in... the answer is no. Its shipped with the OS as part of > the Java Developer Kit. > > Richard D. Dettinger > AS/400 Java Data Access Team > > Democracy's enemies have always underestimated the courage of the American > people. > It was true at Concord Bridge. It was true at Pearl Harbor. And it was > true today. > > Rochester Post-Bulletin > Tuesday September 11, 2001 > > > "Joe Pluta" <joepluta@PlutaBrothers.com>@midrange.com on 10/16/2001 > 10:34:43 AM > > Please respond to java400-l@midrange.com > > Sent by: java400-l-admin@midrange.com > > > To: <java400-l@midrange.com> > cc: > Subject: RE: Data access across libraries > > > > I guess the JDBC native driver team is a different group from the toolbox > team, Fred? I get confused sometimes. Is the native driver located in > jt400.jar, or in jt400ntv.jar? > > > -----Original Message----- > > From: Joe Pluta > > > > on the contrary, the toolbox guys have worked really hard > > _______________________________________________ > This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) > mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/java400-l. > > > > > _______________________________________________ > This is the Java Programming on and around the iSeries / AS400 > (JAVA400-L) mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/java400-l. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.