ALBERDI Ion wrote:
> What happens there is that with Connection Pooling the executeUpdate method
> always returns 0, and that the database is not upgraded.
> I'm currently forced to use the Jdbc3SimpleDataSource class (with this class
> the application runs perfectly) but I would like to use Connection Pools to
> improve the application's performances.
I notice that the default autocommit setting in
org.postgresql.jdbc2.optional.ConnectionPool is false. This is the
opposite of the required Connection default and seems like a bug to me.
If your application is expecting connections obtained from the
datasource to have autocommit on by default, this could be the problem.
In response to
pgsql-jdbc by date
|Next:||From: Kris Jurka||Date: 2004-06-24 06:35:18|
|Subject: Re: PoolingDataSource executeUpdate|
|Previous:||From: Pete Lewin-Harris||Date: 2004-06-23 15:28:05|
|Subject: Blob getBinaryStream issue.|