From: Roy Zuo <roylzuo@...>
Date: 2011-08-01T04:32:24+09:00
Subject: Re: How to connect to and use Postgresql from Ruby

I would personally recommend Sequel, even for performance. Although ruby-pg is
more low level, it is very hard to fine tune every transaction. Sequel by
default does a lot of caching in memory and comes with builtin database
connection pool. These can save great effort reimplementing by yourself and also
boost you application performance. Not to mention Sequel also has got a
memchached plugin already just in case you want it. Using Postgres with Sequel,
you still have access to bind variable and prepared statement functionality
coming from ruby-pg, which can be fine tuned to further improve performance.

Aside from performance, using high level library like Sequel makes your
application more portable and more readable.

Regards,

Roy Zuo

On Mon, Aug 01, 2011 at 04:09:42AM +0900, Chris White wrote:
> 
> On Jul 31, 2011, at 11:54 AM, Chad Perrin wrote:
> 
> > On Mon, Aug 01, 2011 at 03:30:25AM +0900, Chris White wrote:
> >> 
> >> 1) Install Postgres
> >  . . .
> >> 14) Make note to self to fork that repository and push a fix
> >> 15) ???
> >> 16) Profit!
> > 
> > Why not just use Sequel or DataMapper?
> > 
> > -- 
> > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
> 
> Performance, as ruby-pg interfaces directly with libpq. There are also chances that postgres offers specific functionality only accessible through a libpq interface. This comes down to the question of what the specific use case is for interfacing with postgres. 
> 
> Regards,
> Chris White
> Twitter: http://www.twitter.com/cwgem

--