On Tue, Feb 13, 2024 at 1:03 PM Bernd Eckenfels
wrote:
> Phil Steitz wrote on 13. Feb 2024 20:46 (GMT +01:00):
> > Thanks, Gary. I agree with everything below. I think it's best to just
> > leave things as they are.
>
> If it’s plugable the project might not have to care,
> But then how to fix
Phil Steitz wrote on 13. Feb 2024 20:46 (GMT +01:00):
> Thanks, Gary. I agree with everything below. I think it's best to just
> leave things as they are.
If it’s plugable the project might not have to care,
But then how to fix the reported problem? Do we have an idea what’s causing it?
And a
Thanks, Gary. I agree with everything below. I think it's best to just
leave things as they are.
Phil
On Mon, Feb 12, 2024 at 7:25 PM Gary Gregory wrote:
> I've used many JDBC drivers from different vendors, FOSS and
> proprietary, and if I've learned one thing, it is that each is its own
>
I've used many JDBC drivers from different vendors, FOSS and
proprietary, and if I've learned one thing, it is that each is its own
world within the universe of the DBMS it operates in.
It is impossible to write a generic tool; they all end up providing
plugins for DB-specific features, sure, but
In DBCP-595, a change is suggested to force close connections when a fatal
SQL exception has occurred. As of Version 2.2 of DBCP, fatal exceptions
are tracked and the fastFailValidation property can be set to fast fail
validations when a fatal exception has occurred on a connection. This
change
