When source and target column names are different, you can specify an explicit column mapping in the configuration file, to ensure that Post applies row data to the correct target columns.
To use column mapping, you must map every column in a source table to a column in the target table, even if only some source and target names are different. When some columns are mapped but not others, the entry is considered to be a column partition for vertically partitioned replication, and data changes for non-listed columns are not replicated.
The following syntax creates a column map. For more information, see Configure data replication.
datasource_specification | ||
src_owner.table (src_col,src_col,...) | tgt_owner.table (tgt_col,tgt_col,...) | routing_map |
Configuration component | Description |
---|---|
datasource_specification |
The datasource specification. For more information, see Database specifications in a configuration file. |
src_owner.table and tgt_owner.table | The specifications for the source and target tables, respectively. For more information, see Create a configuration file. |
(src_col,src_col,...) |
A list of the source columns. Follow these rules to specify a column list:
|
(tgt_col,tgt_col,...) |
A list of the target columns.
|
routing_map |
The routing map. For more information, see Routing specifications in a configuration file. |
This example contains no case-sensitive columns.
Datasource o.oraA |
|
|
sales.prod (ID,name,vendor) |
mfg.prod (UPC,product,supplier) |
sysB@o.oraB |
This example contains case-sensitive columns.
Datasource o.oraA |
|
|
sales.prod (ID,"name",vendor) |
mfg.prod (UPC,"product",supplier) |
sysB@o.oraB |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center