On Monday, September 22, 2014 8:05:41 AM UTC-7, Sarah Kowalik wrote:
>
> 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?
>
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.
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.
