Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order

From: Andrew Chernow <ac(at)esilo(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Aleksej Saushev <asau(at)inbox(dot)ru>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order
Date: 2008-05-08 02:36:58
Message-ID: 4822674A.7070007@esilo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruce Momjian wrote:
> Aleksej Saushev wrote:
>> The following bug has been logged online:
>>
>> Bug reference: 4053
>> Logged by: Aleksej Saushev
>> Email address: asau(at)inbox(dot)ru
>> PostgreSQL version: 8.3
>> Operating system: NetBSD, but this does no matter
>> Description: libpq documentation should express clearly, that
>> integers are passed in network octet order
>> Details:
>>
>> The documentation on PQexecParams is silent about the precise format,
>> expected by server for binary parameters, it should be more explicit
>> and note that integers are expected in network octet order.
>
> This brings up a good question. Exactly how do users know what format
> _binary_ is? int4 is network byte order, but what about int8, float4,
> inet?
>

They don't have to if they use the libpqtypes library :)

project: http://pgfoundry.org/projects/libpqtypes/
online docs: http://libpqtypes.esilo.com/

andrew

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Christian.Strobl 2008-05-08 09:22:21 reproducible database crash with simple sql command
Previous Message Bruce Momjian 2008-05-08 02:24:13 Re: postgresql in FreeBSD jails: proposal