Versions Compared

Old Version 1

changes.mady.by.user Ashrafuzzaman Purno

Saved on

compared with

New Version 2

changes.mady.by.user Ashrafuzzaman Purno

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Failures and Possible Solutions

Normal Entities

Failure

Solutions

Challenges

AMID conflict

  • Regenarate

  • Ignore row

  • Replace all objectReferenceFor removing

PK conflict

  • Regenaret if UUID

  • Input from the user

  • Replace all FK

  • How to handle composite PK?

Unique conflict

  • Regenarate if UUID

  • Input from the user

  • Set null if nullable

FK conflict

  • Set null if nullable

NULL conflict

  • Regenarate if UUID

  • Input from the user

Wrong type

  • Regenarate if UUID

  • Input from the user

  • Set null if nullable

Wrong length

  • Input from the user

  • Remove extra

  • Set null if nullable

FVP Unique conflict

  • Regenarate

  • Input from the user

System Entities

For simplicity and user-friendliness, we should only consider the AKTOR entity for this section and ignore AMID/PK conflicts for all participant module sub-entities. For the AKTOR entity, we should add some additional options for handling AMID/PK/Unique/FVP Unique conflicts.

Failure

Solutions

Challenges

AMID/PK/Unique/FVP Unique conflict

  • Ignore

  • Ignore the whole subtree for this row

  • Should we consider the possible new sub-entity objects?

  • Should we consider the possible changes for this subtree?

Note: This additional option can be applied to normal entities as well, but would that be meaningful?

Implementation