Description

When status has to be changed at index we load pool that holds indexes.
After loading we update indexes and save to database. Problem is what if between loading and updata another node updated that index?
In this case we can get data loss. The right approach is to add transactions support to ORM and it will work consistently only with DBs that supports transactions. With this PR we are making situation better but it's not solution as it should be with transactions support on ORM level.