June 30, 2015
When we have to insert, update, or delete data, DIET (Dovetail ArchiveManager) is often the tool of choice. Updating an object Typically, when we want to update some data, we just need to define its uniqueness properly. For example, if I wanted to update a business rule property name, I could define its uniqueness as a combination of its object type + name. For example: OBJECT TYPE="prop_name", NAME="commitment case id" UNIQUE_FIELD=obj_type, prop_name FIELDS obj_type=30; /* object type 30 = commit_log */ prop_name="Case ID"; path_name="case_commit2case:id_number"; subtype=0; val_type=0; max_len=255; END_FIELDS END_OBJECT NAME="commitment case id" If I used DIET to import this file, and this prop_name record didn’t exist in the database, then it would do an INSERT, which would create this prop_name record. If I used DIET to import this file, and this prop_name record did exist in the database, then it…
DIET: DELETE + INSERT instead of UPDATE
June 30, 2015
When we have to insert, update, or delete data, DIET (Dovetail ArchiveManager) is often the tool of choice. Updating an object Typically, when we want to update some data, we just need to define its uniqueness properly. For example, if I wanted to update a business rule property name, I could define its uniqueness as a combination of its object type + name. For example: OBJECT TYPE="prop_name", NAME="commitment case id" UNIQUE_FIELD=obj_type, prop_name FIELDS obj_type=30; /* object type 30 = commit_log */ prop_name="Case ID"; path_name="case_commit2case:id_number"; subtype=0; val_type=0; max_len=255; END_FIELDS END_OBJECT NAME="commitment case id" If I used DIET to import this file, and this prop_name record didn’t exist in the database, then it would do an INSERT, which would create this prop_name record. If I used DIET to import this file, and this prop_name record did exist in the database, then it…