[Nitro] Og, adapting postgresql to reorgnaization

Judson Lester nyarly at gmail.com
Fri Feb 23 14:28:37 EST 2007

It shouldn't be too hard.  I'm in the midst of a patch, but when I get
it done, I'll tweak that in.


On 2/22/07, Jonathan Buch <john at oxyliquit.de> wrote:
> Hi,
> >> I'm not sure we can make MySQL thread safe (as I think the standard table
> >> type doesn't react on 'transaction' anyway).  Maybe we put a ruby-level
> >> synchronized around that part?
> >
> > Trouble is, when you have a db involved, process level locks aren't
> > really enough. Slows down execution without real benefit.  This is why
> > MySQL's eternal claim that transactions were unnecessary has always
> > galled me.
> I read this as:  "Lets just leave mysql and it's users alone" ;D
> Allright, I would be happy if you could find a way to make changes so we
> get the old behaviour for psql again, making psql the 'premier' choice
> again. ;)
> Jo
> --
> Feel the love
> http://pinkjuice.com/pics/ruby.png
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general

More information about the Nitro-general mailing list