The following rules should be followed when editing Docebo database. For the sake of clearness, the operations were grouped according to their risk level, i.e. the possibility to harm Docebo functionalities.

OPERATIONS TO BE AVOIDED

• Delete fields or tables from Docebo database      

Deleting fields of a Docebo table or removing the entire table can lead to dangerous and unpredictable consequences, harming the applications' functionalities.

• Rename fields or tables from Docebo database

Renaming a Docebo database field or renaming an entire table is equivalent to deleting the field or table with the original name. Therefore, the consequences are the same listed before.

• Delete, add or edit primary keys or unique indexes

This operation should be avoided since it can lead to unpredictable events, both releasing the constraints or restricting them.
In the former case, it will be possible to insert values which were not meant to be found inside the database.
In the latter case, future inserts which were allowed by the developers could be prohibited.

 

SAFE OPERATIONS

• Adding a field to a Docebo table

This operation can be risky if the following naming convention is not adopted: EXT_XXX, where the "EXT_" prefix is the extension and "XXX" è the requested name.

• Adding a table to Docebo database

This operation is not dangerous at all if the following table naming convention is adopted: EXT_XXX, where the "EXT_" prefix is an extension and "XXX" è is the desired name.