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
It looks like moving from @engine.connection.schema_cache to ::ActiveRecord::Base.connection.schema_cache will exclude tables provided in a secondary schema.
I was using Ransack with ActiveAdmin and Secondbase (to have an admin interface for my Rails app in another app, but share some parts of a database).
Ruby 2.5.0
Rails 5.1.4
Ransack 1.8.7
I understand if this is may not be an urgent/relevant issue.
The commit that added the change is d445755.
I would love to understand what changes in Rails 5.2 it is adapting to, so that I can try submit another solution that will allow gems such as Secondbase to continue to work with Ransack.
If I have missed anything, please let me know and I am happy to add it.
The text was updated successfully, but these errors were encountered:
Hi @varyonic, regarding this issue. Is there any reason we can't use @engine instead of ::ActiveRecord::Base. It looks like we are already using @engine in the same class.
I opened an issue on Secondbase here: customink/secondbase#56.
It looks like moving from
@engine.connection.schema_cache
to::ActiveRecord::Base.connection.schema_cache
will exclude tables provided in a secondary schema.I was using Ransack with ActiveAdmin and Secondbase (to have an admin interface for my Rails app in another app, but share some parts of a database).
Ruby 2.5.0
Rails 5.1.4
Ransack 1.8.7
I understand if this is may not be an urgent/relevant issue.
The commit that added the change is
d445755.
I would love to understand what changes in Rails 5.2 it is adapting to, so that I can try submit another solution that will allow gems such as Secondbase to continue to work with Ransack.
If I have missed anything, please let me know and I am happy to add it.
The text was updated successfully, but these errors were encountered: