Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

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: Thu, 08 May 2008 19:10:52 +0400
  • Message-id: <87od7gsuf7(dot)fsf(at)inbox(dot)ru>

"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.



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group