Network Byte Order Coercion - Mailing list pgsql-interfaces

From Volkan YAZICI
Subject Network Byte Order Coercion
Date
Msg-id 7104a73705051603121f1c35ab@mail.gmail.com
Whole thread Raw
List pgsql-interfaces
Hi,

In libpq example program 3 (testlibpq3.c), an int4 field is converted
to host byte order:

{{{
/* Get the field values (we ignore possibility they are null!) */
iptr = PQgetvalue(res, i, i_fnum);

/** The binary representation of INT4 is in network byte order,* which we'd better coerce to the local byte order.*/
ival = ntohl(*((uint32_t *) iptr));
}}}

(As I saw while reading "An Essay on Endian Order" [1]) I'm not so
familiar with byte orders, but what's the point of coercion in here?
Should we do it in every integer field we retrieved? What's the
[dis]advantages of this? I'd be so appreciated for any explanation.

[1] http://www.cs.umass.edu/~verts/cs32/endian.html

Regards.


pgsql-interfaces by date:

Previous
From: Tom Lane
Date:
Subject: Re: Two seperate problems with libpq - arrays and bytea edit
Next
From: Christoph Haller
Date:
Subject: Re: Network Byte Order Coercion