On Sun, 19 Aug 2007 17:33:16 -0700
"David E. Wheeler" <[EMAIL PROTECTED]> wrote:
> On Aug 19, 2007, at 10:13, Greg Sabino Mullane wrote:
>
> > * Removes a major dependency, allowing the module to be built
> > anywhere.
> >
> > * Faster and cleaner code, as we can create our own paths and
> > functions.
> > For example, we won't need to have all the protocol 2 branching in
> > the libpq code.
> >
> > * (primary reason). We can make up for things missing in libpq, and
> > not have to wait for libpq to adopt them, such as being able to
> > download data in chunks and not have to put everything into memory.
>
> I guess I just assumed that libpq was mature and robust, and that
> reinventing that stuff ourselves would be a lot of work. Perhaps I'm
> wrong?
This seems like a bunch of work for little gain to me. Why not just
patch libpq, perhaps adding a "no protocol 2 branching" compile time
option and the chunking?
I would also be worried about having the new version lag behind any
libpq enhancements in the future.
If nothing else, can we at least have DBD::Pg support both the new
library and libpq at build time?
-------------------------------------------------------
Frank Wiles, Revolution Systems, LLC.
Personal : [EMAIL PROTECTED] http://www.wiles.org
Work : [EMAIL PROTECTED] http://www.revsys.com
