DBSqlSessionFacotry forcing commit

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

frederikherema1

Hi Team,

Anyone an idea why SqlSession.commit(boolean force) is called with argument true, in eg. DbSqlSessionFactory.dbSchemaCheckVersion, instead of the default commit()?
The commit() on DefaultSQLSession will check the autocommit-flag and won't commit when it is on. Forcing just ignores this flag, resulting in an exception.

If there is no particular reason for forcing, I'll use the default commit() instead.

tombaeyens

we're talking about these code pieces in DbSqlSessionFactory

&nbsp;&nbsp;&nbsp; } finally {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (success) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sqlSession.commit(true);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } else {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sqlSession.rollback(true);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sqlSession.close();<br>&nbsp;&nbsp;&nbsp; }
do you know a reason why we should not change that to

&nbsp;&nbsp;&nbsp; } finally {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (success) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sqlSession.commit();&nbsp; // default force is false<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } else {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sqlSession.rollback();&nbsp;&nbsp; // default force is false<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sqlSession.close();<br>&nbsp;&nbsp;&nbsp; }
?