Insert gives foreign key constraint error when correct dependency breaks are listed about condenser HOT 1 OPEN

Hi Ryan! Thanks for your questions. A few answers:

• Condenser doesn't touch your foreign keys — it merely configures the traversal to ignore tables in the ignored tables section. Could you perhaps instead of excluding the table with the self reference add one of the columns to your list of dependency breaks?
• The order of dependency breaks does matter — the FK table is the one that contains the foreign key, the target table contains the primary key. If you have two tables pointing to each other with different FK and PK pairs, you should just pick one of them.
• I'm not sure what you mean by the repo is not public — do you mean your repo? This repo is certainly public, and you're free to fork it and send over a pull request with any work that you have.

Finally, it's notable that Tonic's commercial subsetter solves a lot of these problems without having to over think it — it handles variations of self dependencies, multiple ways of uniquely identifying a row in a table, automatic dependency breaks, and many other features. If you're interested in hearing about it, I'd be happy to point you towards its feature set and how it makes subsetting much easier than condenser's limited feature set.

from condenser.