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

From: Aleksej Saushev <asau(at)inbox(dot)ru>
To: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, "Bruce Momjian" <bruce(at)momjian(dot)us>
Subject: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order
Date: 2008-05-08 15:10:52
Message-ID: 87od7gsuf7.fsf@inbox.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:

> Bruce Momjian wrote:
>> 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?
>
> This is exactly what libpqtypes solves. Not only do we handle
> formatting of binary formats, we provide a level of protection from
> internal format changes for libpq users. See the example here:
> http://libpqtypes.esilo.com/. So, documentation of binary formats
> (including network byte ordering) are not required.

No, it is still required. There's not a single reference to libpqtypes
in Postgres documentation, and libpqtypes isn't part of the distribution,
if I understand it right.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2008-05-08 15:34:32 Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order
Previous Message Merlin Moncure 2008-05-08 14:16:47 Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order