Is AdequateRecord supposed to work with mysql2?

rubyonrails-talk
1

Hi *,

I’ve realised our 4.2.3 application is printing this to the log when doing a basic User.find(1):

SELECT users.* FROM users WHERE users.id = 1 LIMIT 1

When I would’ve expected:

SELECT users.* FROM users WHERE users.id = ? LIMIT 1 [[“id”, 1]]

I tried various things and found out that it only happens when using the mysql2 adapter. The mysql and pg ones seem to print the expected logs.

Does it mean mysql2 doesn’t get the full advantage of the improvements provided by AdequateRecord? Or is it just a difference in the way it logs things?

Thanks!