Skip to content

Conversation

hvlad
Copy link

@hvlad hvlad commented Nov 3, 2022

Behavior depends on option "Switch Off all Ref. Constraints which have a loop".
Now it works as expected, I hope. And not for self-referenced tables only.

When unchecked:

  • when first loop created by foreign keys is found, message with tables and foreign key that makes a loop is displayed and process stopped.

When checked:

  • all loops created by foreign keys are detected and corresponding FK's are disabled before data pump and enabled after
  • destination tables are ordered according to the master-details relationships: independent tables first then tables that depends on them only and so on
  • table nodes in destination tree view are correctly marked as loop parts (by special icon).
  • also such nodes are expanded and nodes of 'to be disabled' FK's are underlined.

hvlad added 4 commits November 3, 2022 19:07
dest tables are ordered according to the master-details relationships - independent tables first then tables that depends on them only and so on.
Loops created by foreign keys are detected and corresponding FK's are disabled before data pump and enabled after.
DDL statement to enable (create) FK is fixed for the case when master table is distinct from detail one.
Table nodes in dest treeview are correctly marked as loop parts. Also such nodes are expanded and nodes of 'to be disabled' FK's are underlined.
It worked for self referenced tables only, now loops of any number of participant tables is detected correctly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant