[ http://jira.jboss.com/jira/browse/JBJCA-16?page=comments#action_12314914
]
youngm commented on JBJCA-16:
-
The managed connection property would be an acceptable solution for me If you
think it would be a good idea.
Mike
> Changing readonly after autoco
[ http://jira.jboss.com/jira/browse/JBJCA-16?page=comments#action_12314913
]
Adrian Brock commented on JBJCA-16:
---
As for you hack:
It would be possible to add a ManagedConnectionFactory property
to control this behaviour.
Allowing you to add somethin
[ http://jira.jboss.com/jira/browse/JBJCA-16?page=comments#action_12314911
]
Adrian Brock commented on JBJCA-16:
---
Correct.
JBoss takes advantage of an obvious (though undocmented)
performance optimization done by all databases.
connection.setAutoCo
[ http://jira.jboss.com/jira/browse/JBJCA-16?page=comments#action_12314910
]
youngm commented on JBJCA-16:
-
Actually, after thinking about this is a bigger problem then I thought. Moving
checkState() above setAutoCommit() won't help if the underlying conn
