Well this is a sticky spot. None of the modules/packages/gems/.... work and here's more. And now I will have three different installations of postgres running on a small macbook. I'm not sure this makes sense anymore.
How is it that Perl has a DBI that is largely libpq independent and Ruby is largely .. not. Sign of maturity of the language? Bryan Blackburn wrote: > On Mon, Oct 06, 2008 at 05:23:19PM -0400, Tom Allison said: >> I'm struggling here between the different mailing lists and postings. >> >> What I would like to get running is the ruby DBI on postgresql 8.3. >> >> macports seems to support 8.1 only. >> rubygems is mostly DOA every time I try to install and run them. >> >> They install without error, but cannot be loaded. >> >> Is there a path I need to set? >> Some other method? >> >> There's a lot pf pages out there talking about a lot of different >> packages available. As near as I can tell - ruby-pg is the one I want >> to install under the DBI library. >> > > For Ruby and DBI, it looks like you want to use the rb-dbi port with the > dbd_pg variant for PostGreSQL. The dbd_pg variant requires the rb-postgres > port which is what brings in postgresql81 unfortantely; there is a ticket > about this: > > <http://trac.macports.org/ticket/12703> > > Bryan > > >> One thing that is a must have is prepared statements for performance. I >> don't think ORM do this very well. > _______________________________________________ > macports-users mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
