Re: Java and Relations DBs..

Brad,


> And finally, the SQLDataSet code does all the connecting to
> the DB, query running, etc.  (John Taylor, it's the one you
> helped me with..)

I'm pretty sure I still have a copy of it at home. Has it changed much? I
think we discussed way back then that SQLDataSet was an interesting
excercise, but would ultimately not be the best approach for a production
application.

You want to avoid having SQLDataSet handle it's own connections,
because --as you've discovered-- that's unworkable in all but the smallest
of applications.

I'd recommend that your data layer have a manager class that handles your
connections, with pooling support. This manager class would follow the
Factory pattern. You would request your result set from the data manager,
which, in turn, would create your new SQLDataSet --passing in a connection
to the class constructor-- and return the new object to the requestor.


John Taylor