Hi
It is a long time for now where "Compare Table Data" has the same functionality. The problem is when I compare 2 or more table with dependencies in between (master-detail, master-detail-detail ... etc) the tool order the result as group of DML statements for each table, where DELETE comes first then UPDATE then INSERT like this:
-- TABLE T1
-- Deleting ...
-- Updating ...
-- Inserting ...
-- xxx row(s) total
-- xxx row(s) read
-- xxx row(s) deleted
-- xxx row(s) inserted
-- xxx row(s) updated
-- TABLE T2
-- Deleting ...
-- Updating ...
-- Inserting ...
-- xxx row(s) total
-- xxx row(s) read
-- xxx row(s) deleted
-- xxx row(s) inserted
-- xxx row(s) updated
When T1 is a detail table and T2 is a master table, some of the inserts fails, likewise some of the deletes from master table fails.
It would be better if there is a way to organize DML statements like this skeleton:
1. Delete all detail records.
2. Delete all master records.
3. Update all detail/master records (in most cases it doesn't matter which comes first, but if it is an option to select which comes first, it is better).
4. insert all master records.
5. insert all detail records.
Of course with the same functionality right now when I select just one table from result grid (show only DML statements for that table).
Regards.
It is a long time for now where "Compare Table Data" has the same functionality. The problem is when I compare 2 or more table with dependencies in between (master-detail, master-detail-detail ... etc) the tool order the result as group of DML statements for each table, where DELETE comes first then UPDATE then INSERT like this:
-- TABLE T1
-- Deleting ...
-- Updating ...
-- Inserting ...
-- xxx row(s) total
-- xxx row(s) read
-- xxx row(s) deleted
-- xxx row(s) inserted
-- xxx row(s) updated
-- TABLE T2
-- Deleting ...
-- Updating ...
-- Inserting ...
-- xxx row(s) total
-- xxx row(s) read
-- xxx row(s) deleted
-- xxx row(s) inserted
-- xxx row(s) updated
When T1 is a detail table and T2 is a master table, some of the inserts fails, likewise some of the deletes from master table fails.
It would be better if there is a way to organize DML statements like this skeleton:
1. Delete all detail records.
2. Delete all master records.
3. Update all detail/master records (in most cases it doesn't matter which comes first, but if it is an option to select which comes first, it is better).
4. insert all master records.
5. insert all detail records.
Of course with the same functionality right now when I select just one table from result grid (show only DML statements for that table).
Regards.