On 11/23/05, Dick Davies <rasputnik@gmail.com> wrote:
> DB connection pooling doesnt' make much sense for Rails.
> Generally you have fastcgi children, each with their dbhandle, which
> are themselves started and stopped by the webserver as needed.
This is true running under FastCGI (though connection timeouts can
still be an issue). Under other environments, such as WEBrick or
using ActiveRecord standalone, this isn't always the case. There is
work being done towards an adapter pool for ActiveRecord, see
http://dev.rubyonrails.org/ticket/2162
Tom
_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails