Table of Contents

Search

  1. Preface
  2. Introduction to PostgreSQL Connector
  3. Connections for PostgreSQL
  4. Mappings and mapping tasks with PostgreSQL Connector
  5. PostgreSQL objects in mapping tasks
  6. Lookup transformation
  7. SQL transformation
  8. Migrating a mapping
  9. PostgreSQL SQL ELT optimization
  10. Data type reference

PostgreSQL Connector

PostgreSQL Connector

Use a different object path for the migrated mapping

Use a different object path for the migrated mapping

After you migrate the mapping, you can use a different object path to run the mapping from the new environment.
In this scenario, before you migrate the mapping, you can change the object metadata or the runtime attributes to reflect the object path in the migrated environment. You do not have to edit or update the mapping in the new environment.
As a rule, when you specify the schema and table in the advanced properties or object properties,
Data Integration
honors the attributes in the following order of precedence:
  1. SQL override
    . The SQL statement to override the default query generated from the specified source type in the Source or Lookup transformation in a mapping.
  2. Custom query
    . The SQL statement to reduce the number of columns to query in the Source or Lookup transformation in a mapping.
  3. Runtime advanced attributes
    . The advanced properties such as schema name and table name in the Source, Target, or Lookup transformation in a mapping.
  4. Connection attributes
    .The schema attribute in the connection properties.
  5. Object metadata
    . The object type selected in the Source, Target, or Lookup transformation in a mapping.

0 COMMENTS

We’d like to hear from you!