Closed vineelvineel closed 2 months ago
This error is caused because the API for creating an ActiveRecord::Associations::AliasTracker
has changed in edge rails. It now wants to eat a connection pool rather than a connection. Knowing nothing about ransack's internals, from what I can tell it shouldn't need to use this API directly, and should just ask it's ActiveRecord::Relation
to create a fresh AliasTracker
instead.
I have a PR to fix in ransack here
This makes so much sense.
I can confirm, this works. I no longer get the with_connection
error.
Hitting the issue as well. Any ETA on PR merge?
Any updates on this? I have other dependencies that require me to upgrade Rails, but Ransack is throwing a wrench in the equation for me.
I am using edge rails and it fails with this rails commit()
i am getting this error when i use ransack queries. When i use AR queries, the error does not happen.