Re: Java and Relations DBs..

["Larry Loen" <lwloen@xxxxxxxxxx>]

>No doubt [connection pooling] should be handled by the Java environment,
IMHO, and
>probably will one day.

Check out WebSphere.  I lose track of all the distinctions involved between
the various levels of the product (since I don't have to pay for it ;-) ),
but I think you'll find connection pooling is available in WebSphere and
probably at all levels of it.

As long as your application is sufficiently simple, writing your own
"pooling" function is not terribly difficult.  Certainly, to prototype
things while running in Microsoft land, it probably can be made to work
well enough for the pre-OS/400 testing.  If you like WebSphere, you can
probably pre-plan so you can encapsulate a quick-and-dirty version for
basic test before the migration.

I still suspect you're going to find that you have a problem with the
Order(N something) effect sooner or later, probably when you scale it up
(unless I've misunderstood your description).

As for the DB versus Table terminology thing, "it's a fair cop" as the
British put it.  Too many years on OS/400.


Larry W. Loen  -   Senior Linux, Java, and iSeries Performance Analyst
                          Dept HP4, Rochester MN