DATA - Data Architecture > Data and Database Design > Synchronizing logical and physical models > From the Logical Model to the Physical Model > Protecting Objects
Protecting Objects
You can protect an object so that synchronization will have no impact on it. This excludes the object from synchronization without it disappearing.
There are two object protection modes; one upstream and the other downstream.
Frozen mode
"Frozen" mode concerns the target object, that which results from synchronization.
When you freeze a relational model table, you also freeze all child objects of this table: no child object is created, modified or deleted by synchronization.
You can freeze objects:
• Before running synchronization, in the database editor.
• When running synchronization, in the options presented in the wizard. See Step 3: Protecting objects.
Realized mode
"Realized" mode concerns the source object of synchronization.
An object is said to be realized if it produces object creation at synchronization.
An object not realized does not produce object creation at synchronization but is treated as an abstract object. See Abstract entity.
By default, all objects are realized.
You can exclude a source object from synchronization selecting the "Not realized" column on the object in question in the synchronization wizard. This action is available on entities, attributes and associations. The "realized" or "not realized" action is propagated to child objects.
Not realized entity example
The "Article" entity has an association to the "Article Type" entity.
The "Article Type" entity is said to be "not realized".
At synchronization, the "Article Type" entity does not produce creation of a table. In the"Article" table, the foreign key to "ArticleType" is not created; however the "Code_Type_Article" column is created.