V
Valeriy Bashkatov
Guest
Hi Satya, [quote user="Satya Prasad"] This can be easily handled in Pro2 by NOT deploying the delete triggers on the OpenEdge database. This means, if you delete any records on the OpenEdge database those records won’t be deleted on the target (ORACLE) database. [/quote] I don't agree with that. NOT deploying delete triggers will NOT solve this. Also, you can't disable saving a note about deleting a record if you use OE CDC instead of triggers. The fact is that if you simply disable delete triggers, you certainly will not delete such records from Oracle through Pro2, but when a record is deleted from OpenEdge, its RECID is released, which can be assigned to another new record in OpenEdge. As a result, when such a record appears, Pro2 will save it in place of the existing "deleted" record in Oracle. And this was solved by the Pro2 developers with the Logical Deletes: 2) When LOGICAL_DELETE_TABLES is enabled and a record is deleted from the source table, the corresponding record will remain in the foreign database table but is flagged as deleted via its PRROWID. For example, Original : 0x0000000000000356 PRROWID after record is deleted from the source table: D-0x000000000000035620180504-56806
Continue reading...
Continue reading...