A programming error during an older refactoring lead to the scheduler working with a single monolithic transaction. This could cause unnecessary resource contention, plus undesired rollback of all previous operations in the event of an exception during scheduling. bzr revid: odo@openerp.com-20130701163532-8bekn7sbb99ua08c