Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 24403475908 for ; Fri, 12 Jul 2002 11:26:46 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g6CFQmAl010004; Fri, 12 Jul 2002 11:26:48 -0400 (EDT) To: "Warren W. Gay VE3WWG" Cc: Jan Wieck , PostgreSQL mailing list Subject: Re: Wish List: Client access to NUMERIC/DECIMAL type functions In-reply-to: <3D2EDFBA.1010704@cogeco.ca> References: <3D2ED844.80800@cogeco.ca> <3D2EDBE9.D3FCA87A@Yahoo.com> <3D2EDFBA.1010704@cogeco.ca> Comments: In-reply-to "Warren W. Gay VE3WWG" message dated "Fri, 12 Jul 2002 09:55:06 -0400" Date: Fri, 12 Jul 2002 11:26:48 -0400 Message-ID: <10003.1026487608@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200207/75 X-Sequence-Number: 2884 "Warren W. Gay VE3WWG" writes: > If I use the binary interface, I now have to convert your "decimal" number > to someone else's format, so I can do something with it. > Oracle or INFORMIX OTOH, provide the user access to > routines to manipulate their builtin data types. We don't encourage people to use the binary interface at all, because we don't want to get involved with handling cross-platform representational differences (not to mention version-to-version changes in internal representation). Therefore there's no reason to export routines that would handle the server-internal binary representatin. regards, tom lane