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
{{ message }}
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.
On models with Binary properties, which #dump the data with force_encoding("BINARY"), the DataObjects adapter doesn't pay attention to the encoding and builds a "UTF-8" encoded string containing non-UTF-8 data. This manifests in an explosion when using the New Relic middleware, which introspects queries.
The text was updated successfully, but these errors were encountered:
Actually, not 100% if this is happening during query execution, or during query logging. It explodes when new relic receives the query as a log entry, which means it's already executed in the DB. I'd have thought with MySQL (which we use), DataObjects adapter would be using prepared statements, but I may be wrong. Haven't got a huge amount of time to look into it right now.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On models with
Binary
properties, which#dump
the data withforce_encoding("BINARY")
, the DataObjects adapter doesn't pay attention to the encoding and builds a "UTF-8" encoded string containing non-UTF-8 data. This manifests in an explosion when using the New Relic middleware, which introspects queries.The text was updated successfully, but these errors were encountered: