[
https://issues.apache.org/jira/browse/DBCP-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565273#action_12565273
]
Raghu commented on DBCP-259:
----------------------------
This is excellent Phill.....
I really didnt think the setting the value of two boolean parameters can change
the course of a program to this extent....
when i am doing this -
con.setAutoCommit(false);
con.setReadOnly(true);
I am getting the desired exception and now i can see some
consistency.......Thanks for the help where i am struggling with this for past
2 days...but do you think the order is so much important...i dont want to drag
the issue..this would be my last comment....
:-)
> 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.
