On Sat, Nov 15, 2008 at 5:44 PM, 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?
I don't know if the support was dropped deliberately, merely that the preferred deployment option is pg. To get it working again you'll need to simply run the tests and fix the tests. I realise that's a little trite, but there weren't many huge changes made. Perhaps use git bisect to find it? > Thanks, > Stefan > > > > -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
