Steve Ebersole Hi Steve, I am thinking about the async/batch operations support in 2LC SPI, and I wonder: What is the reason for StorageAccess.lockItem() invocations? IIUC this is invoked before the SQL is generated and sent to DB, but since these changes are not visible until the transaction commits, implementation could do the same rather in StorageAccess.update()/remove(). Or would there be a difference?

And on a bit different matter: is EntityDeleteAction.doAfterTransactionCompletion() not calling StorageAccess.unlockItem() when the transaction fails an oversight or is the lock held locked by purpose?