This has been fixed.
You should also notice that this performs better in 3.2.3RC1
compared with 3.2.1 if you always do readonly on the connection.
ReadOnly is now set lazily, so it will only pass the request to the db
the first time. After that it will remain as readonly until you
don't
On Mon, 2003-10-27 at 09:58, Andrew May wrote:
This has been fixed.
You should also notice that this performs better in 3.2.3RC1
compared with 3.2.1 if you always do readonly on the connection.
ReadOnly is now set lazily, so it will only pass the request to the db
the first time.
This is the diff (fairly trivial):
http://cvs.sourceforge.net/viewcvs.py/jboss/jbosscx/src/main/org/jboss/resource/adapter/jdbc/WrappedConnection.jpp?r1=1.1.2.8r2=1.1.2.9
Thanks, that does the trick. Once again I can search obscure bibliographic databases :)
-Andrew
On Wed, 2003-10-22 at 10:46, Andrew May wrote:
Hi,
We've just upgraded to 3.2.2 from 3.2.1 and we're having a problem with one our JDBC
connection pools.
We're using a BASIS bibliographic database that only allows you to query the
database if
the JDBC connection is read-only. After we
Hi,
We've just upgraded to 3.2.2 from 3.2.1 and we're having a problem with one our JDBC
connection pools.
We're using a BASIS bibliographic database that only allows you to query the database if
the JDBC connection is read-only. After we get a connection from a Datasource we're
calling
Possibly. Open a bug report on sourceforge with the code fragment that
is no longer working.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Andrew May wrote:
Hi,
We've just upgraded to 3.2.2 from 3.2.1 and we're having a problem with
