On Dec 28, 4:08 pm, Iñaki Baz Castillo <[email protected]> wrote: > El Martes, 29 de Diciembre de 2009, Jeremy Evans escribió: > > > It probably could, but Sequel's postgres adapter supports postgres and > > postgres-pr in addition to pg (not to mention previous versions of > > pg), and backwards compatibility for those must be kept. As the > > connect_poll method exists in previous versions of pg, but is broken, > > I don't think Sequel can support it until a new version of pg is > > released. After a new version of pg is released, if the version of pg > > being used can be checked, you could conditionally use the > > connect_poll in the adapter's connect method if pg is being used and > > the pg version properly supports it. > > Ok, I've installed the new commit for 'pg' solvinf this issue and it behaves > correctly. The following example works for me: > > http://bitbucket.org/m/attch/2009/12/test_ruby_db_drivers_block_in_co... > > I hope that the problem you mean in "connect_poll" is fixed now (but I'm not > sure as I have no idea why it was broken before). > > So let's wait until an official release :)
You should also request the pg maintainer to maintain a versioning scheme for pg that is outside of rubygems, similar to Sequel's Sequel.version. Even though Sequel is distributed as a gem, Sequel doesn't depend on rubygems, and therefore cannot use the rubygems API to determined which pg gem is loaded. 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.
