Remove getRemovedForced and forceRemove from BaseEntityContext

Description

getRemovedForced and forceRemove in BaseEntityContext are dangerous: as they don't check if the data are int the database before to remove them they may result in a tuple does not exist exception. We should remove them and make sure that the transactions using them are getting the data from the database before to try to remove them.

We should also change BaseEntityContext.getRemoved to only return entities that were originally fetched from the database.

Status

Assignee

Gautier Berthou

Reporter

Gautier Berthou

Labels

None

Fix versions

Priority

High
Configure