Hi Jeremy,
The first thing you need to do is figure out how to connect using the
> underlying driver (the mysql gem in this case). If you can report how to
> do so here, I can probably tell you how to do so with Sequel.
>
In sequel, I'm currently trying:
@db = Sequel.connect('mysql://user:[email protected]/database')
I'm not sure what you mean - are you suggesting I connect directly via
https://rubygems.org/gems/mysql instead of using sequel?
> You could also try switching to the mysql2 adapter, and see if the problem
> exists there.
>
This is a possible route. I see they have a mechanism for turning
secure_auth off as part of the connection.
Sarah
--
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.
