Re: Java and Relations DBs..

["Brad Stone" <brad@xxxxxxxxxxxx>]

> You don't know that for sure.  It depends on a couple of
> things:
>
> 1.  Whether you have a WHERE clause or not in your query.

Yes, there is a where clause.  I can see why this would slow
things down.

>
> 2.  Internal details of the data base and who implemented
> what inside the
> DB itself.

It's a single table.  What would the rest of the DB have to
do with it?  Or are you talking about indexes, and the like
on the single table?  Or does DB=Table in this case (see, I
called a table a DB on the iSeries too, but since it's
confusing in the Java world, I try to stick to more
"worldly" terms.. <bg>)

I believe my biggest bottleneck, as David mentioned, is
probably opening and closing a connection each time.  Since
i'm accssing an Access DB I use an ODBC bridge.. not the
best way to do things, but when it's all you've got to play
with, it has to do.

I've looked at connection pooling in the past, and see how
it would help.  But, since it seems there are so many
implentations of pooling, and how it could be built into the
drivers, it's something that I don't care to get into.  No
doubt should be handled by the Java environment, IMHO, and
probably will one day.

So do I really want to write pooling classes?  No.  May I
try?  Yes, if decent examples could be found.  :)
Implementing should be fairly easy and trasparent to the
rest of my applications.