In ADB to ADB scenario, when I define parent-child relationship at both publisher and subscriber side, why do I need child table mapping?
Article ID: KB0084433
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Database | - |
| Not Applicable | - |
Description
Resolution:
That's because publisher side and subscriber side can use different table names. If publisher side and subscriber side have the same table name, no table mapping is needed. Otherwise, when subscriber receives the message, the subscriber doesn't know in which table to put the child data unless there is a child table mapping that exists.
That's because publisher side and subscriber side can use different table names. If publisher side and subscriber side have the same table name, no table mapping is needed. Otherwise, when subscriber receives the message, the subscriber doesn't know in which table to put the child data unless there is a child table mapping that exists.
Issue/Introduction
In ADB to ADB scenario, when I define parent-child relationship at both publisher and subscriber side, why do I need child table mapping?
Environment
Product: TIBCO Adapter for ActiveDatabase
Version: ALL
OS: All
--------------------
Feedback
Yes
No
Powered by
