[
https://issues.apache.org/jira/browse/DBCP-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565029#action_12565029
]
Phil Steitz commented on DBCP-259:
----------------------------------
Your understanding may not be correct, depending on the JDBC driver and
database. PoolableConnectionFactory will invoke the underlying Connection's
setReadOnly(true) method when a PoolableConnection with defaultReadOnly = true
is activated. What that means in practice regarding what can be done with the
connection, what is optimized, etc. depends on the driver. The driver
documentation should say whether or not and how readOnly connections are
supported.
> defualtReadOnly not working in conncetion pooling
> -------------------------------------------------
>
> Key: DBCP-259
> URL: https://issues.apache.org/jira/browse/DBCP-259
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.2.1
> Environment: commons-pool 1.2, jdk 1.4
> Reporter: Raghu
>
> Hi All
> I am trying to set up a connection pooling using Jakarta commons-dbcp
> 1.2.1....
> When defaultReadOnly property is set to true and if my understanding is
> correct i would not be able to perform update,insert or delete operations.
> When i set defualtReadOnly as true in the constructor
> PoolableConnectionFactory which looks like -
> poolableConnectionFactory = new PoolableConnectionFactory(
> connectionFactory, connectionPool, null,
> "sql query", true, true);
> But still i am able to perform the delete or insert opertations where i am
> expecting to throw an excpetion.
> Am i missing some thing or is ther anything fishy???
> Thanks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.