[PATCH] [DBCP] Support for other default Connection properties

[Russ Milliken <RM...@smartops.com>]

The attached patch provides support for the three currently unsupported
Connection properties ("catalog", "transaction isolation", and "type
map").  To keep backwards compatability, the defaults for these
newly-supported properties are only used if explicitly set by the
client.  Thus, the hard-coded "defaults for the defaults" are never
used.

Enjoy!

-Russ

-----Original Message-----
From: Rodney Waldhoff [mailto:rwaldhoff@apache.org] 
Sent: Wednesday, February 19, 2003 6:17 AM
To: Jakarta Commons Developers List
Subject: Re: [DBCP] Support for other default Connection properties?


As far a I know, these additional properties simply aren't exposed at a
"default" level (although as you note, are accessible via the regular
API).

Patches welcome.

On Wed, 19 Feb 2003, Russ Milliken wrote:

> Is there support for default Connection properties other than ReadOnly

> and AutoCommit?  You can create a PoolableConnectionFactory specifying

> defaultReadOnly and defaultAutoCommit at construction time, or may 
> change the defaults at any time thereafter via API methods.  This is 
> good, but what of the other properties on Connection, e.g. Catalog, 
> TransactionIsolation, and TypeMap?  Are these in DBCP somewhere else, 
> and if so, shouldn't these all be in one place, i.e., 
> PoolableConnectionFactory?
>
> -Russ
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org