[Feature Request] Make it easier to understand "Ensure you aren't referring to labels that don't exist on associations."

kmitov · September 25, 2022, 7:12pm

Loading the fixtures. Got

Foreign key violations found in your fixture data. Ensure you aren't referring to labels that don't exist on associations.

The message is not helpful. It’s late at night and I’ve missed label/reference somewhere. Stupid mistake but looking at it for a few minutes already and can not figure out what I messed up. It will be great if the message is a little more descriptive. I will be willing to put some time on trying to show at least which is the label or the reference.

Do you think this will be possible? Is this something that has a chance of being accepted?

sdubois · September 27, 2022, 10:36am

Maybe this is what you are looking for?

github.com/rails/rails

Show reason for referential integrity failure

rails:main ← danini-the-panini:patch-2

opened 12:34AM - 23 Apr 22 UTC

danini-the-panini

+48 -14

### Summary Currently, if there is a referential integrity error in your fixt…ures, it will throw an error. However, the original error message from postgres is swallowed in `all_foreign_keys_valid?` and returns false. This gives the developer very little information on where to start debugging. My proposed solution is to raise the original exception from the underlying adapter for postgres, and raise a similar error from the SQLite adapter. ### Other Information Stack overflow explaining the issue: https://stackoverflow.com/questions/71054865/tips-for-debugging-fixture-foreign-key-errors-in-rails

kmitov · September 27, 2022, 6:21pm

Yes thanks. This could work.

Do you think there is a chance of it being merged.

sdubois · September 28, 2022, 9:58am

I have no idea You could maybe bring this PR to the attention of maintainers by sharing it in the Discord forum.