Closed PuntoDiGoccia closed 1 year ago
Hi @PuntoDiGoccia,
Thank you for using the gem and your kind words.
You seem to have two " broken " associations; for example, they miss "class_name" options.
Unfortunately, it's hard for me to say which associations are broken.
Probably, one is related to "Private::Asset::AssetModel." Both errors are associated with a single association. Unfortunately, the stack trace doesn't give much information about how to find that broken association.
I will implement a checker for that.
Looking at the stack trace, you will see that the issue happens in ActiveRecord (not in DatabaseConsistency).
Please let me know if this information is anyhow helpful to you.
Hi @PuntoDiGoccia,
I've just merged: https://github.com/djezzzl/database_consistency/pull/205
It does two things:
It was released with version 1.7.13. Please try it, and let me know if that helped you with your issue.
Have a great day!
Hi @PuntoDiGoccia,
I've just merged: #205
It does two things:
- adding a new checker that will help you to find invalid associations that point to undefined models
- stop raising an error for ForeignKeyTypeChecker
It was released with version 1.7.13. Please try it, and let me know if that helped you with your issue.
Have a great day!
Hi @djezzzl , yep, that helped get a better understanding of the issue, thanks!
I'm testing database_consistency (great project BTW) first time on my app . The report is being generated but starts with:
Here's the dumped file:
We have a multi-DB setup, some entities are saved in one, other in another.
Keep it up, thanks