Anonymization fails midway if two tables have a circular referential integrity

[satyamag]

Even though it is poor schema design there have been real world examples where it does happen.

[satyamag]

One workaround is to drop referential integrity checks. In Mysql (similar technique exists for postgres) this can be done by executing the following on the db

SET FOREIGN_KEY_CHECKS = 0

IMPORTANT: Ensure you set it to the original value once anonymization is complete.

[sunitparekh]

closing the issue, since we are not working actively on this and there is a work around.

[wasabigeek]

@sunitparekh it seems the corresponding Postgres options are:

• run ALTER TABLE on every table or defer each foreign key individually
• execute 'SET session_replication_role=replica;' for the session

The latter is a lot easier, but I need to set it within the actual session. Is there a way to include commands in the connection?

Also, what is DisableReferentialIntegrityDatabase? Was this an option you were thinking of adding?

data-anonymization/lib/utils/database.rb

Line 12 in 6ccfda4

class DisableReferentialIntegrityDatabase < ActiveRecord::Base