On Sat, Nov 15, 2008 at 8:44 AM, Stefan Lang <[EMAIL PROTECTED]> wrote: > > 2008/11/15 Andrew Kaspick <[EMAIL PROTECTED]>: >> >> The pg gem is what you should be using now. > > postgres-pr was easier to deploy - put it in vendor > and be done. Building a C extension on/for the server > can be a hassle. > > And neither pg nor ruby-postgres build with Ruby 1.9. > > What was the reason for dropping postgres-pr support, > and what needs to be done to make it work again?
It wasn't intentionally dropped. It doesn't implement the #transaction_status method. Upgrade to the latest postgres-pr, which has this method, and you'll be back up and running. Also, the C drivers have worked with 1.9 since January 2008. Best, jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
