On Dec 28, 8:47 am, Iñaki Baz Castillo <[email protected]> wrote: > El Lunes, 28 de Diciembre de 2009, Jeremy Evans escribió: > > > As you can see, it's a problem with the ruby-mysql driver. > > It also occurs with the postgress 'pg' driver :( > Annoying...
Annoying yes, but not something that Sequel has control over. If there are timeout options that Sequel isn't using, please send in a patch, otherwise, you might want to bring this up with the pg maintainer. In most cases, if it can't connect, it should eventually timeout. I just tried with both the postgres and mysql adapters, and both timed out after 75 seconds. So maybe you just aren't waiting long enough. Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
