Hello,
I am using an automation script that uses import activities to insert into an external MySQL database table with a duplicate key constraint. The import appears to fail (the subsequent records aren’t inserted) after the first duplicate key error. I would like it to continue. If I was creating the insert statement myself I would accomplish this with the IGNORE keyword. Is there some way to configure this behavior in the automation script? OnError is set to continueOnError. I am using Toad Data Point 3.3.0.932 Beta because of other 3.2 limitations with respect to MySQL.
Sorry, currently there’s no configuration available for such import. Our import engine uses simple insert statements to update target table. We need to add an option to use insert ignore . I created CR105739 for it.
Message was edited by: Kiki
Sorry, currently there’s no configuration available for such import. Our import engine uses simple insert statements to update target table. We need to add an option to use insert ignore . I created CR105739 for it.
Message was edited by: Kiki
Ok, my work around is to create a staging table in MySQL without the constraint to import into from my Oracle query, then use and “Execute Script” activity to do an INSERT to the MySQL table with constraints from the MySQL staging table using the “INGNORE” keyword and then delete records from the staging table.
Glad to see you have a work around. We will try to offer a solution in the future.
Debbie