El Lunes, 28 de Diciembre de 2009, Jeremy Evans escribió: > On Dec 28, 11:41 am, Iñaki Baz Castillo <[email protected]> wrote: > > El Lunes, 28 de Diciembre de 2009, Iñaki Baz Castillo escribió: > > > I've checked 'pg' driver separately. When the conenction is lost (i.e. > > > DB restart) a new "connect" is required: > > > > Well, nothing new as it's the same as with mysql driver. > > However Sequel reacts when mysql connection is lost. > > First, If you plan on doing additional investigating, please refrain > from posting until you have a complete issue report. Posting 6 > separate responses each with new information just makes my job more > difficult. :)
Sure, I'm really sorry. > Second, this is a bug. Sequel should be converting the PGErrors to > Sequel::DatabaseErrors, and if possible, recognizing which errors > indicate disconnection, and removing those connections from the pool > (by raising Sequel::DatabaseDisconnectError). > > Try the patch at http://pastie.org/759309.txt and let me know if it > fixes the errors. Unfortunatelly I cannot apply the patch as I get errors: File to patch: postgres.rb patching file postgres.rb Hunk #3 succeeded at 223 with fuzz 1. Hunk #4 FAILED at 234. 1 out of 5 hunks FAILED I've tryed the master branch and also the last gem 3.7.0. -- 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.
