Posted
about 15 years
ago
by
Michael Granger
With the news of RubyForge's changing role, I'm taking this opportunity to move all ruby-pg development to Bitbucket. I've taken over primary support of the 'pg' library from Jeff Davis, who will remain associated with the project to give me advice
|
Posted
almost 17 years
ago
by
Jeff Davis
This project is looking for people who can help improve windows portability. No unix-specific libraries are used, all the problems are related to the C extension build process. Please contact the project if you have a little time to help out!
|
Posted
about 17 years
ago
by
Jeff Davis
I have committed some changes to both ruby-pg (the new module) and ruby-postgres (the old module) so that it would be easy for ActiveRecord to support them both.
Now I have submitted a patch ( http://dev.rubyonrails.org/ticket/10948 ) to
|
Posted
about 17 years
ago
by
Jeff Davis
I split the modules 'postgres' and 'pg' into two separate parts of the SVN repository, and will release them as separate gems.
'pg' is the newer module, which is a much better design. It's encouraged for use when an ActiveRecord adapter is not
|
Posted
about 17 years
ago
by
Jeff Davis
This latest release offers Ruby 1.9 support for both the 'pg' and 'postgres' modules, and many improvements.
The new 'pg' module has been substantially improved and stabilized. The API still is not set in stone, so I'd like to get some feedback
|
Posted
about 17 years
ago
by
Jeff Davis
Ruby-pg is now the official home of the "postgres" gem.
Please report any problems.
This gem contains some important fixes, including the ability to build against PostgreSQL 8.3.
|
Posted
almost 18 years
ago
by
Jeff Davis
I have begun ruby-pg, the fork of the ruby-postgres project.
I am receiving a lot of great feedback: people with ideas, people with patches, or people just saying that they are happy to see that someone is improving the interface between the world's best programming language and the world's best database!
|