it was just a little test, no need to handle this situation
thx, sr
"C. Ferguson" <c_ferguson_at_rationalconcepts.com> wrote in message
news:3C38DA1F.DB5817_at_rationalconcepts.com...
> Hmmm,
> this won't be germane to the discussion on the whys of fluctuating
execution
> times,
> but a comment on your openConnection method.
>
> I would not rely on driver being the controlling flag for your
connection
> validity during your applications complete session.
>
> You may run into the case of the connection going null or closing due to
> events beyond your (application's) control. In that scenario, your driver
> string would still hold information from an initial connect, but would
prevent
> your application from reattaining the connection if it had gone south
(think db
> crash).
>
> Instead use:
> if (dbCon == null || dbCon.isClosed()) {
> // get connection
> }
Received on Mon Jan 07 2002 - 10:59:29 CST
