Issues with Missing PK and FK Constraints.

[nareneee]

Hi Darold,

We are currently performing our migration in two phases: first for non-BLOB tables and then for BLOB tables, by specifying tables in the ALLOW parameter of the configuration file. However, we are encountering missing primary and foreign keys in PostgreSQL after the migration. For instance, we generated the constraint files separately for non-BLOB and BLOB tables, and imported both files into PostgreSQL. Despite this, we still see mismatches in constraints on the Postgres side. When we disable the ALLOW parameter and run the migration for all tables together, the issue does not occur.

Could you please help us understand why PK and FK constraints are missing when we limit the tables using the ALLOW parameter?

Thank you for your support.