Typically this is the job of the connection broker, when you return the
connection the broker should make sure it's "clean", otherwise just
close the connection when you are done with it.
If you are leaving it open, then I suggest you do a finally after every
operation and clean it up.
Dave
On Tue, 2003-05-06 at 21:11, David Wall wrote:
> > > These warning messages are stored up until you read them, or call
> > > clearWarnings().
> > >
> > > This is all correct behavior AFAICT.
>
> What's the "correct" or "typical" way that people get these warnings out? I
> mean, who calls clearWarnings() on a connection? Is it part of an exception
> handler? When an SQLException is thrown, we do process it and often display
> the potentially chained exceptions, but we've never cleared something. How
> do you even know that a warning is pending?
>
> David
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
--
Dave Cramer <Dave@micro-automation.net>
