search.data.gov.au migrators are going to collide with normal migrators

Problem description

With all this content stuff we’ve been doing, we’ve been writing Flyway migrators that we build into our migrator images, and also writing manual scripts for data.gov.au, with the idea being that when the upgrade for data.gov.au happens, we can run the manual scripts then the migrators.

However because in some cases both scripts are running an INSERT for the same content item id, this is going to break when we run the migrator. Which is annoying.

So we need to modify the migrators we’ve done to have ON CONFLICT DO NOTHING on the INSERT statements.

This will be fine in all our prod deployments because we haven’t released the migrators yet, but it’s going to make dev.magda.io very very unhappy. So we’ll have to manually fix that with flyway repair when the change gets merged. But that’s OK.

Acceptance Criteria

• All the migrations for v0.0.50 can successfully run after all the search.data.gov.au-specific sql scripts for v0.0.50 have run.

[t83714]

I think 3 would be fair estimate~

[aneesha09]

Guys - please add an estimate to this one, thanks