RE: Java and Relations DBs..

["Price, Chris" <chris_price@xxxxxxxxx>]

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Brad,

At a risk of massively over-simplifying things, if you have a single user
application over an access database, why do you ever need to open more than
one Connection?

Once open, store it in a static field somewhere, and all your classes should
be able to use it.

This should work for any client/server type project, as the client JVM only
needs to worry about it's own connection to the Database (The Database has
to do the hard bit of managing multiple users).

Connection pooling seems like a hammer to crack a nut in this case.

Chris.
 -----Original Message-----
From:   John Taylor [mailto:jtaylor@rpg2java.com]
Sent:   09 January 2002 22:31
To:     java400-l@midrange.com
Subject:        Re: Java and Relations DBs..

Brad,

Have you considered creating an "SQLManager" class that is responsible for
maintaining your connections, and constructing and returning SQLDataSet
objects as required?


John Taylor

----- Original Message -----
From: "Brad Stone" <brad@bvstools.com>
To: <java400-l@midrange.com>
Sent: Wednesday, January 09, 2002 2:56 PM
Subject: Re: Java and Relations DBs..


> Ok, here's my question now.
>
> To create a container, I return a result set to the
> container class from an "SQLDataSet" class.  This SQL class
> does the query and returns the result set so I can load my
> container class.
>
> I'm finding that (and suspected this) that connection
> pooling really isn't helping me here.  Since I create a new
> SQLDataSet class for each creation of the container.  This
> means a new connection pool is created each time, etc.
>
> Any hints?


_______________________________________________
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.