On Tuesday, September 23, 2014 1:17:59 AM UTC-7, Sarah Kowalik wrote: > > Hi Jeremy, > > Yes. Sequel just uses the underlying driver to connect. As I'm not >> familiar with mysql's secure_auth and don't know how to fix the problem off >> hand, the easiest way for me to help you is for you to tell me how you can >> connect with the underlying driver. Once I have that information, I should >> be able to tell you how to connect via Sequel. Maybe the mysql gem doesn't >> support turning secure_auth off, in which case there is nothing Sequel >> could do to fix the problem. >> > > Sounds fair. I wasn't able to work out how to make the MySQL driver work > with secure_auth, but I did discover that the reason I'm having problems > with this is because I have MySQL 5.6 on my system, rather than the 5.5 > that most linux distributions have. This newly default option is described > at > https://dev.mysql.com/doc/refman/5.6/en/mysql-command-options.html#option_mysql_secure-auth > . > > MySQL2 allows you to set :secure_auth = true/false during the connection > (https://github.com/brianmario/mysql2#connection-options) >
Sequel passes Database options to Mysql2::Client.new, so as long as you use the mysql2 adapter and specify :secure_auth => true in your Database connection options, you should be OK. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
