Re: libpq and prepared statements progress for 8.0

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: <pg(at)fastcrypt(dot)com>
Cc: "Greg Stark" <gsstark(at)mit(dot)edu>, "Oliver Jowett" <oliver(at)opencloud(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: libpq and prepared statements progress for 8.0
Date: 2004-09-17 13:56:09
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4306511@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Dave Cramer [mailto:pg(at)fastcrypt(dot)com]
> Sent: 17 September 2004 14:52
> To: Dave Page
> Cc: Greg Stark; Oliver Jowett; Tom Lane; Merlin Moncure;
> pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] libpq and prepared statements progress for 8.0
>
> Interesting,
>
> I'd like to know more about the issues you are trying to
> solve? Seems counter productive for all of us to attempt this
> independently

Mainly lack of time :-)

SSL and v3+ protocol support are the primary issues. If we can use
libpq, then obviously we don't have to worry about them any more. Other
than that, there isn't then a great deal left to do with the driver
(that I can think of) as the vast majority of the API is there and
working, and we have unicode support as well now.

> What about the .net driver ? Yet another protocol implementation ?

Yeah, native, managed C# code.

Regards, Dave

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2004-09-17 14:26:18 Re: Others applying patch queue patches
Previous Message Dave Cramer 2004-09-17 13:52:04 Re: libpq and prepared statements progress for 8.0