our db does not support bulk insert statements, so we disabled this feature in the ProcessEngineConfiguration. As alternative we tried to use ExecutorType.Batch offered by MyBatis.
So we customized the DBSqlSession to always use the ExecturotType.Batch. Is there a risk of performance overhead where scenarios ar not dlealing with multi inserts/updates?
Does it makes sense to introduce two MyBatis SqlSessions in flowables DBSQLSession: one with ExecutorType.SIMPLE and one with ExecutorType.BATCH, depending on the number of rows to be inserted/updated?
We tried it out and we have issues we foreing key releations. it is not visible for the other until the transaction is comitted. Any proposal how to avoid that?