Figure 0.10 Version Control
If time has been spent setting up overrides for columns, for example, setting flags to 'N', or setting end dates to a high value, it is not desirable to re-do this work if the database schema has been changed during system development. Version control allows you to keep the work you have done, while updating the table and column formats that have been modified.
Version control works with an open database schema and a target database schema. The open schema is the latest up-to-date version of the schema. The target is the older schema you have previously been working with in TurboData. Version control compares the table names and column names on the two schemas. If the names match, the target schema is updated. If there is a table or column on the open schema that does not exist on the target, it will be created on the target. If there is a table or column on the target that does not exist on the open schema, it will be deleted from the target.
Warning: TurboData cannot detect a table name or column name change. It will treat them as two separate tables or columns. It will delete the old object from the target, and recreate it with the new name.
How to Perform Version Control
