Phil Steitz wrote:
Josh Wyatt wrote:
Phil Steitz wrote:
Sorry. Strike last response. Misread the post. False, which is the
default, should work. Please open a new JIRA for this.
Thanks!
Phil
Thanks for the note- I created one, DBCP-282:
https://issues.apache.org/jira/browse/DBCP-282
For reference, I did try setting the parameter to "true," and the new
behavior is a litany of 'SET TRANSACTION READ ONLY' instead of the
original 'SET TRANSACTION READ WRITE,' so looks like I am setting the
parameter in the correct location in the configuration, but no love on
an 'unset' value being honored.
Can I assume this will be as easy a fix as DBCP-178?
The problem has been fixed in the source to be released in DBCP 1.3.
Phil
Thank you for the investigation and the resolution.
Is there any way for me to get this fix into my production environment? I
could not even find a way to download the 1.3 source tree.
Thanks,
Josh
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
