Hi Konni,
when a JDBC connection is requested by Castor using local transactions,
the first thing it does is to call connection.setAutoCommit(false). This
behaviour can not be convigured at the moment as we have not seen any
sense in that. Setting auto commit to true would prevent to be able to
roll back any transaction in my opinion. Am I missing anything here?
For your reference there are 2 calls to connection.setAutoCommit(false):
- org.castor.persist.LocalTransactionContext (line 69)
- org.exolab.castor.jdo.engine.SQLStatementCreate (line 470)
The second occurence is only used to query last identity for some of the
key generators.
Having said that it would be easy to make auto commit configurable if
there is demand.
Regards
Ralf
Konni schrieb:
Is it possible to set the autocommit flag in the castor-jdo config-file or in
the java-program ? I'll explain what the problem is.
We have a DB2 database on a iSeries system (IBM). When I use castor as it is
configured by default, then I have to journalize the corresponding database
tables on our iSeries system. Otherwise I would get the SQL error "SQL7008"
when I will perform any transaction. I would like to avoid this, since we
don't journalize any of our database tables.
BR,
Konni
--
Syscon Ingenieurbüro für Meß- und Datentechnik GmbH
Ralf Joachim
Raiffeisenstraße 11
72127 Kusterdingen
Germany
Tel. +49 7071 3690 52
Mobil: +49 173 9630135
Fax +49 7071 3690 98
Internet: www.syscon.eu
E-Mail: [EMAIL PROTECTED]
Sitz der Gesellschaft: D-72127 Kusterdingen
Registereintrag: Amtsgericht Stuttgart, HRB 382295
Geschäftsleitung: Jens Joachim, Ralf Joachim
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
