Page Comparison

...

Table of Contents

style	none

Failures and Possible Solutions

Normal Entities

...

Conflicts

AMID

Type	Description	Solutions

Challenges

Solutions(NO)

Example
UNIQUE	An object with this

AMID

value for this field already exists

Genarate

Replace all objectReference

Erstatt alle objektreferanser

PK

An object with this primary key already exists
Single PK only for now

Genarate if UUID

Replace all FK
How to handle composite PK?
Should we generate other types? If so then how?

Erstatt alle fremmednøkler

Input from the user

Requires user interaction

Unique

An object with this value for this field already exists

Genarate if UUID

Should we generate other types? If so then how?

Input from the user

Requires user interaction

Set null if nullable

FVP Unique

An object with this value for this field already exists
Root entities only for now

Genarate

Input from the user

Requires user interaction

Set null if nullable

FK

The parent object not found
Not yet supported

Set null if nullable

Required

Input from the user

Requires user interaction

Wrong Type

Applicable for
- AMID system field
- Primary key field (Single PK for now)
- Any other unique fields
- Root entity fields with field value pattern

GENERATE
SET_BY_USER
SET_NULL
FAIL

There is an object of entity A with AMID 821df1d4-3ed8-463e-a9a3-ea841be60f81 in the system. When trying to import this object again or any other object of entity A with the same AMID.

There is an entity A which has a field identifier with a field value pattern. The system already has an object of entity A with identifier A-0001. When trying to import any object of entity A with the identifier A-0001 again.

FK

The parent object referred by this field not found
Applicable for fields that are used to store links to their parent objects
Not yet supported

IGNORE
SET_NULL
FAIL

Entity A has a sub-entity Entity B. Entity B then will have a field like ref_a which will store the id of its parent object of Entity A. When trying to import an object of Entity B which has a value in the ref_a field, but there is no object of Entity A with that id.

REQUIRED

No value present for this required field

Genarate

Generate dummy values if not UUID or FVP

Applicable for AMID system field Primary key fields Any other non-nullable fields	GENERATE SET_BY_USER FAIL	Entity A has a primary key field `id`. When the import file for entity A contains an object which has no value set for the field `id`.
TYPE	Value type not compatible with the field type

Genarate

Generate dummy values if not UUID or FVP

Input from the user

Requires user interaction

Set null if nullable

Wrong Length

GENERATE SET_BY_USER SET_NULL FAIL	Entity A has a field `id` of type `integer`. When the import file for entity A contains any value for the field `id` which is not an `integer`.
LENGTH	Text length is longer than the limit

Trim extra

Input from the user

Requires user interaction

Set null if nullable

System Entities

For this section, we need to consider the system root entities like AKTOR, TAG, etc. and ignore AMID/PK conflicts for all sub-entities. We have added options for handling AMID/PK/Unique/FVP Unique conflicts for the system root entities.

Failure

Solutions

Challenges

AMID/PK/Unique/FVP Unique conflict

Ignore

Applicable for `varchar` fields with a length set	TRIM_EXTRA SET_BY_USER SET_NULL FAIL	Entity A has a `varchar` field `name` with `length` `10`. When the import file for entity A contains any value for the field `name` with a `length` greater than `10`.
Root System Entity UNIQUE	Applicable for root system entities (AKTOR, TAG, RESTRICTION)	IGNORE REPLACE_WITH_EXISTING	The system already has an AKTOR with `identifikator` `AKT-0001`. When trying to import any data that has an AKTOR with `identifikator` value `AKT-0001`.

Solutions

Type	Description	Challenges
GENERATE	Generates a new value based on the field type or using the field value pattern Not available for PK and UNIQUE if field type is not `UUID`	For AMID, replace all `objectReference` For PK, replace all FK How to handle composite PK? Should we generate PK for other types? If so then how?
SET_BY_USER	Input from the user Not applicable for conflicts that are gathered during import	Requires user interaction
SET_NULL	Applicable for nullable or not required fields
SET_NULL_OR_REGENERATE	Set `null` if nullable or generate a value (dummy) based on the field type Applicable for conflicts that are gathered during import
TRIM_EXTRA	Trim the extra part Applicable for `varchar` fields with a length set
IGNORE	Ignore this object and it’s descendants Highest precedence	Ignore the whole subtree for this

row

object as well

Highest precedence

Replace with the conflicted row

Replace all objectReference and FK

REPLACE_WITH_EXISTING

Ignore this object and it’s descendants but keep the relation objects (AKTOR_RELASJON, TAG_MAPPING, OBJECT_RESTRICTION)
Import relation objects but change the relation to connect to the conflicted row
2nd highest precedence

Ignore the whole subtree for this object as well
Keep the relation objects but change their FK

2nd highest precedence

Should we consider the possible new sub-entity objects?
Should we consider the possible changes for this subtree?

Replace with a chosen row (Maybe later)


FAIL	Throw an error and abort Applicable for conflicts that are gathered during import

Implementation

We can divide the implementation into four key steps.

...

After clicking the Resolve button a new tab will be opened. In the tab, there will be options to choose how do you want to proceed. There will be options present per conflict type. Either you can gather the conflicts beforehand, or gather and solve them while importing, and the third option is to mix both, meaning gather some types beforehand but resolve the rest while importing.

Conflict Type	Default Solutions (Used while importing)	Description
AMID	Generate	Generate a new UUID
AMID	Fail	Throw error and abort
PK	Generate	Generate a new UUID Available if all are UUID
PK	Fail	Throw error and abort
Unique	Generate	Generate a new UUID Available if all are UUID
Unique	Fail	Throw error and abort
FVP Unique	Generate	Generate a new FVP
FVP Unique	Fail	Throw error and abort
FK (Not supported yet)	Set Null	Set `null` if nullable
FK (Not supported yet)	Fail	Throw error and abort
Required	Generate	Generate a dummy value
Required	Fail	Throw error and abort
Wrong Type	Set Null or Generate	Set `null` if nullable or generate a dummy value
Wrong Type	Fail	Throw error and abort
Wrong Length	Trim Extra	Trim the extra part
Wrong Length	Fail	Throw error and abort
System Entity	Generate	Generate a new UUID or FVP
	Ignore	Ignore this row and it’s subtree
	Replace with the conflicted row	Ignore this row and it’s subtree (Without the relation objects) Import relation objectss but change the relation to connect to the conflicted row
	Fail	Throw error and abort

...

If all the types are set to resolve at import time then the Resolve and Import button will be shown. In this case, the 3rd step is not needed anymore. Otherwise, you can proceed to the 3rd step by clicking the Gather Conflicts button.

...

Support Excel import
Support Composite PK Support and FK conflict
Generate other types than UUID
Optimize using temporary table and/or files rather than the memory
Add more types of solutions

Versions Compared

Old Version 15

New Version Current

Key

Failures and Possible Solutions

Normal Entities

Conflicts

System Entities

Solutions

Implementation