Re: [Proxool-developer] Driver specific interfaces

[Bill H. <bi...@lo...>]

CHR,

On Wed, 2004-03-24 at 09:44, Christian Nedreg=E5rd wrote:

> A quick check on interface based JDBC implementations:
> SQLServer: No
> Sybase: Yes
> postgreSQL: Yes
> MySQL: No
> DB2: No

What does that mean? A "no" means that the driver doesn't implement any
driver specific interfaces?

> ...and then you have Oracle. Here the confusion is complete

Sounds par for the course.

> We should certantly NOT deprecate DriverManager.getConnection and
> friends.=20

Eh? How can we deprecate a JDK method? I'm confused.=20

I did mention deprecating ProxoolFacade.getDelegateConnection() and
getDelegateStatement(). From what you say below that is probably not a
good idea.

> I am very uncertain wether this stuff is going to add value or
> confusion. Please consider this again

It won't do any harm. If a public interface for the object is available
it will be used. If it isn't then it behaves like it did before.

> By the way; your example below won't work with the Oracle driver we
> use (8.1.7.0.4).=20
> OracleConnection is a class there...

Hmm. Well that's a shame. But just to be clear, it will "work" in as
much as Proxool will behave itself. It just means that the cast won't
work and you'll have to use ProxoolFacade.getDelegateConnection(). Which
is probably what you meant.

In summary: I think that exposing the public interfaces is still a good
idea. It won't be as useful as I originally thought because not all
drivers use public interfaces, but it's certainly a step forwards.

- Bill