Handling renamed objects and columns
When your database schema changes, you can import those changes and update your Dataedo documentation schema in a similar way you imported it.
Renamed objects
When an object is renamed in the database, Dataedo behaves just as if it was deleted and created with a new name.
It marks the object with the old name as deleted and creates a new one with the new name.
Renamed columns, keys, etc.
Renamed columns (and keys, parameters, etc.) work the same as objects - an element with an old name gets marked as deleted, and an element with a new name is created. And again, copy the description from the old to the new element if required and delete the old element.
Cleansing documentation - renamed objects
After the change, you will end up with two objects in the repository. You may want to:
- Copy documentation (manually) from the old to the new object.
- Remove the old object from the repository.
Cleaning up documentation - renamed columns
Similarly to objects, you might want to:
- Copy the description and other fields from the old to the new column.
- Remove the old column from the repository.
Renaming objects manually
You can avoid the hassle of copying the description from the old to the new object if you know (before the import) that the object name changed. You can use the design option to rename the object in the repository to match the name (and schema) in the database.
This object will be changed to manual. It will switch to physical during import.
