Foreign key nullification about evil-seed HOT 3 CLOSED

Got it. This is feature to keep referential integrity.

If you don't interested in persons that a Car is borrowed to, then you won't have them in the database. In that case, if you try to insert record to person_car_borrows with identifier that is missing from persons (and you have foreign key in place) then database will throw an error that this value violates referential integrity. So it is better to nullify foreign key value if we know that we're not going to reference anything.

from evil-seed.

I believe that reason for this is avoiding errors with foreign key constraints in the database. So it actually may be a feature (but not sure).

Please provide your EvilSeed configuration.

Possible workarounds: instruct evil-seed to dump Person, Cars, and PersonCarBorrows separately.

from evil-seed.

The configuration is something like

EvilSeed.configure do |config|
  config.root("Person", id: ids) do |root|
    root.exclude(/\.translations/)
  end

  config.root("Car") do |root|
    root.exclude(/\.translations/)
    root.exclude(/car\.person_car_borrows\.person\..*/)
  end
end

So the problem might actually be related to this exclude root.exclude(/card\.person_car_borrows\.person\..*/)?
The only reason I do that exclude is that it is not of my interest to export all "Persons" that a Car is borrowed to, but now that I'm looking at it, maybe the exclude should be root.exclude(/card\..*/) to avoid the PersonCarBorrows altogether from the Cars?

EDIT: Just to add that Person has defined in it

has_many :person_car_borrows, dependent: :restrict_with_exception

EDIT2: Ok I think that the problem is just related with the order of the configuration? It just worked now by changing the order, so thanks!

from evil-seed.