--[populateTableWorker] error: insert or update on table "abc" violates foreign key constraint

[amatosg]

hi!

As this is a migration, it is save to say that the data is consistent, so it would be a good idea to disable triggers on each table before inserting the data, once all data has been migrated, enable all triggers as suggested here: https://stackoverflow.com/a/38113838/1917300

Maybe I'm missing something?

[AnatolyUss]

Hi Alejandro,
Thanks for posting the issue.
The data transfer happens before enabling of keys, unless you're migrating the data into a preset schema.
Could you send me your configuration (/nmig/config/config.json)?

• Connection details may be excluded.

[amatosg]

I'm using a preset schema. I'll send the config when I get home. thanks!

EDIT: I remember only changing the connection details and adding "*" for preset tables. Other than that, config is the same

[AnatolyUss]

Ok, understood. Definitely, it is "triggers" issue. I'll fix it asap.

…

On Tue, Sep 17, 2019, 7:20 PM Alejandro Matos ***@***.***> wrote: I'm using a preset schema. I'll send the config when I get home. thanks! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#67?email_source=notifications&email_token=ADHR7N66MMZXIIXQVN3HWELQKD7VFA5CNFSM4IWSHCS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65CVII#issuecomment-532294305>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADHR7N4LZMQ5QQCUKL4TJB3QKD7VFANCNFSM4IWSHCSQ> .

[AnatolyUss]

Hi,
The issue seems to be fixed.
Please, use the latest release (v4.0.2).