El Lunes, 28 de Diciembre de 2009, Jeremy Evans escribió: > 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,
The problem is that the DB drivers block the entire process, so it's not possible to use green threads at the same time to control it. Nothing to do in Sequel side I think. > otherwise, you might want to bring this up with the pg > maintainer. Yes, I've already reported it: http://github.com/oldmoe/mysqlplus/issues/#issue/3 http://bitbucket.org/ged/ruby-pg/issue/14/pgconnconnect-blocks-forever-if-the- db-host-is I've also created a simple script to check it: http://gist.github.com/264921 > 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. Yes, I didn't wait enough. However in my case it took more than 3 minutes (both "mysqlplus" and "pg" drivers). Perhaps it depends on the SO. Regards. -- Iñaki Baz Castillo <[email protected]> -- 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.
