You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rails recognize my association and everything is working fine.
If I avoid :inverse_of param I can get to make RA work but the parent_category field is a text_field instead of the desired dropdown and children_categories is not shown.
The field children_categories appears if I force it from the rails_admin.rb initializer but shows me a dropdown select instead of multiple select.
EDIT : Like my previous issue, I'm on Rails 3.2 ... if it matters
I don't know if it's a known issue or if I'm making something wrong, but I'll try to figure it out.
The text was updated successfully, but these errors were encountered:
Well, avoiding the :inverse_of finally worked. I admit I can't tell why it didn't worked before since I don't remember doing any action between the time it failed and now that it works apart from modifying the way I declare my relations.
There are a few limitations to inverse_of support:
They do not work with :through associations.
They do not work with :polymorphic associations.
They do not work with :as associations.
For belongs_to associations, has_many inverse associations are ignored.
Hi,
I've been stuck with a ActiveRecord::InverseOfAssociationNotFoundError while trying to make a self join in some model.
The model relevant code :
Rails recognize my association and everything is working fine.
If I avoid
:inverse_of
param I can get to make RA work but the parent_category field is a text_field instead of the desired dropdown and children_categories is not shown.The field children_categories appears if I force it from the rails_admin.rb initializer but shows me a dropdown select instead of multiple select.
EDIT : Like my previous issue, I'm on Rails 3.2 ... if it matters
I don't know if it's a known issue or if I'm making something wrong, but I'll try to figure it out.
The text was updated successfully, but these errors were encountered: