Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 2A28D47589E for ; Mon, 15 Jul 2002 16:57:57 -0400 (EDT) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.5.9) with ESMTP id 1577799; Mon, 15 Jul 2002 13:57:57 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Tom Lane , "Christopher Kings-Lynne" Subject: Re: Sorry.. Date: Mon, 15 Jul 2002 14:01:38 -0700 X-Mailer: KMail [version 1.4] Cc: pgsql-sql@postgresql.org References: <7344.1026703661@sss.pgh.pa.us> In-Reply-To: <7344.1026703661@sss.pgh.pa.us> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200207151401.38968.josh@agliodbs.com> X-Archive-Number: 200207/223 X-Sequence-Number: 8601 Christopher, > In the bad old days when we couldn't distinguish explicit from implicit > cast functions, I was wary of adding new cast pathways. Too many > implicit casts and you have no type system at all. But in 7.3 there > should be no reason to object to an explicit-only cast from numeric > to text or vice versa. I'd suggest making the explicit cast of numeric to text be the exact=20 equivalent of: SELECT btrim(to_char(numeric, '999,999,999,999.9999999999')) or similar. --=20 -Josh Berkus Aglio Database Solutions San Francisco