Uploaded image for project: 'hops'
  1. HOPS-1371

Remove getRemovedForced and forceRemove from BaseEntityContext

    Details

    • Type: Bug
    • Status: In Progress (View workflow)
    • Priority: High
    • Resolution: Unresolved
    • Affects versions: None
    • Fix versions: 2.8.2.9
    • Labels:
      None
    • Sprint:

      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.

        Attachments

          Activity

            People

            • Assignee:
              gautier Gautier Berthou
              Reporter:
              gautier Gautier Berthou
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: