Documentation
public interface DatabaseMapping
The user interface also provides features for interacting with the database mapping. See the Administration guide for more information.
Repository.getDatabaseMapping()| Modifier and Type | Method and Description |
|---|---|
void |
renameDisabledColumn(SchemaNode aNode,
String columnNewName,
String columnOldNameOrNull)
Renames a disabled column of a table.
|
void |
renameLivingColumn(SchemaNode aNode,
String columnNewName)
Renames an active column of a table.
|
void renameLivingColumn(SchemaNode aNode, String columnNewName) throws OperationException
If the table exists in several mapped modes (history, replication, relational), the change will affect all of them.
aNode - the data model node for the element to be renamedcolumnNewName - the target name for the columnOperationException - if the new name cannot be assigned because of database constraints.void renameDisabledColumn(SchemaNode aNode, String columnNewName, String columnOldNameOrNull) throws OperationException
If the table exists in several mapped modes (history, replication, relational), the change will affect all of them.
aNode - the data model node for the element to be renamedcolumnNewName - the target name for the columncolumnOldNameOrNull - This parameter can be passed as null in most cases.
If a non-null parameter value is provided, it has to match the existing
name for this column;
this extra verification makes non-ambiguous the choice of the column to be
renamed; indeed, if the element has undergone several
type evolutions, it might be represented in the database by several
columns with distinct names.OperationException - if the specified parameters do not map to exactly one database column,
or if the new name cannot be assigned because of database constraints.