Re: postgresql protocol v3

Furthermore, postgresql-v8 supports per column binary results with the 
extended query protocol, which would be nice.

I'll get cracking on postgresql-socket-v3. Any other volunteers, let me 
know.

Thanks,

Cyrus

On Dec 4, 2004, at 9:03 AM, John DeSoi wrote:

>
> On Dec 4, 2004, at 11:17 AM, Cyrus Harmon wrote:
>
>> So I've been trying to add blob and prepared-query support to the 
>> various flavors of the postgresql drivers. I've got the libpq version 
>> working to a first approximation, but I'd like to get the 
>> postgresql-socket stuff working too. Unfortunately, in order to do 
>> the prepared query stuff I need protocol v3. I'm assuming there are 
>> some folks who would like to continue to use v2 for talking to 
>> postgres 6 databases (or whenever protocol v3 appeared). Any 
>> objections to adding a postgresql-socket-v3 module to clsql? It seems 
>> a little silly to have three separate modules for talking to 
>> postgresql databases, but I'm not sure there's a better alternative. 
>> Suggestions? Comments?
>
> The v3 protocol did not appear until version 7.4. I think a separate 
> module for v3 would be the best approach and could eventually replace 
> the other two approaches over the long term. It is very nice to work 
> with and provides access to a lot of features that won't be possible 
> with the v2 protocol. In particular, error handling can be much 
> improved because you can get actually error numbers instead of trying 
> to parse (localized) error strings for what went wrong.
>
> Best,
>
> John DeSoi, Ph.D.
>