We can encounter several failures while importing content/data in Asta7. So far , our approach for handling failures has been to throw an exception and abort the import. However, But this approach is not user-friendly , as most of the failures are recoverable.
...
| Table of Contents | ||
|---|---|---|
|
Conflicts
The conflicts can be divided into several categories. They are as follows
UNIQUE
Most of the conflicts can be put into this category. This conflict can happen for fields in entities that are marked as UNIQUE. In most cases, this conflict will happen if you try to import an already existing object. An entity can have the following types of unique fields
AMID
Every entity implicitly has a system field called AMID (_amid). This field uniquely identifies an object of a particular entity and project. This field is of type UUID.
Primary Keys
Every entity should have one or more user-defined unique identifiers as well. These fields are marked as primary keys in the entity. These fields can be of any type.
| Info |
|---|
We are considering a single primary key for now |
Unique
Entities can have other fields as well which are marked as unique by the user. These can be of any type as well.
FVP Unique
Root entity fields that have a Field Value Pattern associated with them are considered UNIQUE as well.
Example
There is an object of entity A with AMID 821df1d4-3ed8-463e-a9a3-ea841be60f81 in the system. If you try to import this object again or any other object of entity A with the same AMID, this conflict will arise.
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. If you try to import any object of entity A with the identifier A-0001 again, this conflict will arise.
...
Type | Description | Solutions |
|---|---|---|
AMID |
|
|
PK |
|
|
UNIQUE |
|
|
FVP_UNIQUE |
|
|
FK |
Entities can have fields that are used to store links to their parent objects. These fields are called foreign key fields. If any foreign key field contains a link to a parent object that does not exist this conflict will trigger.
| Info |
|---|
Not yet supported |
Example
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. In case you are 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, then this conflict will arise.
...
|
|
REQUIRED |
...
|
...
|
...
|
...
Example
...
|
...
| |
TYPE |
Each field in an entity has a type (UUID, TEXT, etc.). If the provided value type of a field in the import does not match the field type then this conflict will happen.
Example
Entity A has a field id of type integer. if the import file for entity A contains any value for the field id which is not an integer then this conflict will arise.
Solutions
|
|
LENGTH |
VARCHAR fields can have an optional length property set. This property dictates how long the text value can be. If any value exceeds the length then this conflict will happen.
Example
Entity A has a varchar field name with length 10. If the import file for entity A contains any value for the field name with a length greater than 10 this conflict will arise.
...
|
|
Root System Entity
|
...
|
|
...
Example
The system already has an AKTOR with identifikator AKT-0001. If you try to import any data that has an AKTOR with identifikator AKT-0001 this conflict will arise.
...
|
Solutions
Type | Description | Challenges |
|---|---|---|
GENERATE |
|
|
SET_BY_USER |
|
|
SET_NULL |
| |
SET_NULL_OR_REGENERATE |
| |
TRIM_EXTRA |
| |
IGNORE |
|
|
REPLACE_WITH_EXISTING |
|
|
FAIL |
|
...