Preface
Introduction to PostgreSQL Connector
- PostgreSQL Connector assets
Connections for PostgreSQL
Mappings and mapping tasks with PostgreSQL Connector
PostgreSQL objects in mapping tasks
Lookup transformation
- Rules and guidelines for uncached lookups
SQL transformation
- Rules and guidelines for SQL transformations
Migrating a mapping
- Use the same object path for the migrated mapping
- Use a different object path for the migrated mapping
  - Migration options
  - Rules and guidelines for migrating a mapping
PostgreSQL SQL ELT optimization
Data type reference

PostgreSQL Connector

Back Next

Use the same object path for the migrated mapping

If you want the migrated mapping in Org 2 to use the same object path as in Org 1, you must maintain the same schema and table in the PostgreSQL connection for Org 2.

For example, if you have two different connections, Connection1 used for Org 1 and Connection2 used for Org 2, the object path for the schema and table name must be the same in both the connections:

Connection1: SCHEMA1/TABLE1

Connection2: SCHEMA1/TABLE1

In this scenario, you do not need to override the schema and table in the advanced properties.

Rename Saved Search

Table of Contents

PostgreSQL Connector

PostgreSQL Connector

Use the same object path for the migrated mapping

Use the same object path for the migrated mapping