X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C07C6D1B1BC for ; Mon, 14 Jun 2004 16:27:58 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 88138-03 for ; Mon, 14 Jun 2004 19:27:55 +0000 (GMT) Received: from smtp-out1.xs4all.nl (smtp-out1.xs4all.nl [194.109.24.11]) by svr1.postgresql.org (Postfix) with ESMTP id 1DEF2D1B19B for ; Mon, 14 Jun 2004 16:27:51 -0300 (ADT) Received: from xs1.xs4all.nl (xs1.xs4all.nl [194.109.21.2]) by smtp-out1.xs4all.nl (8.12.10/8.12.10) with ESMTP id i5EJQuJg034292; Mon, 14 Jun 2004 21:26:56 +0200 (CEST) Received: from xs1.xs4all.nl (jtv@localhost.xs4all.nl [127.0.0.1]) by xs1.xs4all.nl (8.12.10/8.12.10) with ESMTP id i5EJOffr019736; Mon, 14 Jun 2004 21:24:41 +0200 (CEST) (envelope-from jtv@xs4all.nl) Received: (from jtv@localhost) by xs1.xs4all.nl (8.12.10/8.12.9/Submit) id i5EJOfPD019735; Mon, 14 Jun 2004 21:24:41 +0200 (CEST) (envelope-from jtv) Date: Mon, 14 Jun 2004 21:24:41 +0200 From: "Jeroen T. Vermeulen" To: Eliot Simcoe Cc: pgsql-interfaces@postgresql.org Subject: Re: libpq binary transfer of the numeric data type Message-ID: <20040614192441.GH87999@xs4all.nl> Mail-Followup-To: Eliot Simcoe , pgsql-interfaces@postgresql.org References: <405AD008-BE30-11D8-B774-000A959CE7FA@mac.com> <20040614185117.GG87999@xs4all.nl> <56927E3C-BE35-11D8-9907-000A959CE7FA@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56927E3C-BE35-11D8-9907-000A959CE7FA@mac.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/36 X-Sequence-Number: 4964 On Mon, Jun 14, 2004 at 03:02:10PM -0400, Eliot Simcoe wrote: > The platform I am developing on is big endian, so this shouldn't be an > issue as far as I understand. That's right. The data are all in network byte order, i.e. big-endian. FWIW I'm doing the C++ frontend and I decided not to touch binary transfers at all for now. There are other reasons as well, but lack of a clear and stable description was one of them... Jeroen