Fix encoding detection error for MySQL applications using a connection proxy #3313
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Applications using MySQL with DB connection proxies (seen when using active_record_host_pool, but may apply to others that employ the same pattern) cannot currently use RailsAdmin's export feature, as
instance_variable_get
returnsnil
- resulting in aNoMethodError
when#encoding
is called from the template after a user clicks to export from a list.Proposed change
raw_connection
returns the same connection as the@connection
instance variable, and works withDelegator
s that wrap the connection.raw_connection
itself is supported across all maintained versions of Rails, and resolves the issue mentioned above.