Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order
- From: Bruce Momjian <bruce(at)momjian(dot)us>
- To: Aleksej Saushev <asau(at)inbox(dot)ru>
- Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
- Subject: Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order
- Date: Thu, 8 May 2008 11:34:32 -0400 (EDT)
- Message-id: <200805081534(dot)m48FYWR26563(at)momjian(dot)us>
Aleksej Saushev wrote:
> "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.
Agreed.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Home |
Main Index |
Thread Index