ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick <ric...@gmail.com>
Subject clarification on docs pg 53 transaction control methods
Date Sun, 23 Aug 2009 21:20:30 GMT
pg 53 Tansaction Control Methods

"By default iBATIS does not actually commit unless it detects that the
database has been changed by a call to insert, update or delete. If
you’ve somehow made changes without calling these methods, then you
can pass true into the commit and rollback methods to guarantee that
it will be committed"

What would be an example of changes done 'without calling these
methods' where you might want to force a commit with true?  Are you
referring to an external manipulation of the row in question from
outside the app (ie manual update.)

I assume it won't hurt anything to always be safe and call
commit(true) on the inserts,updates, deletes ?

To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org

View raw message