Re: pulling libpqtypes from queue

From: tomas(at)tuxteam(dot)de
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andrew Chernow <ac(at)esilo(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pulling libpqtypes from queue
Date: 2008-04-16 06:48:54
Message-ID: 20080416064854.GA16338@www.trapp.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Apr 15, 2008 at 10:57:37AM -0400, Merlin Moncure wrote:
> On Tue, Apr 15, 2008 at 10:48 AM, <tomas(at)tuxteam(dot)de> wrote:
> > On Tue, Apr 15, 2008 at 09:48:37AM -0400, Merlin Moncure wrote:
> > > On Tue, Apr 15, 2008 at 9:36 AM, Alvaro Herrera
> > > <alvherre(at)commandprompt(dot)com> wrote:
> >
> > > > I expect you intend to get at least the hooks in, right?

[...]

> libpqtypes was designed to handle this with our without hooking. (the
> 'hooking' debate was mainly about exactly how libpq and libpqtypes was
> going to be separated).
>
> libpqtypes had a superclassing concept (not much discussed on the
> lists) where you could introduce new type handlers that wrapped
> existing ones and was desgined exactly for things like this.

That sounds cool. So in a way you do have the hooks. That would be the
libpqtypes without the types, no?

> keep an
> eye on our upcoming pgfoundry project.

I sure will.

Thanks
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFIBaFWBcgs9XrR2kYRAgHNAJ9L59j9eHw0EkZ5Imzg5txAX1lF4ACcCbgS
6bgw0sejoFlCbHXvV55kimo=
=QuvI
-----END PGP SIGNATURE-----

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Brendan Jurd 2008-04-16 06:52:22 Re: [HACKERS] Text <-> C string
Previous Message NikhilS 2008-04-16 06:36:16 Re: Lessons from commit fest