Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f03KaI719208; Wed, 3 Jan 2001 15:36:18 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f03KanB17686; Wed, 3 Jan 2001 15:36:50 -0500 (EST) To: "mdavis@sevainc.com" cc: "'pgsql-sql@postgresql.org'" , "'pgsql-general@postgresql.org'" Subject: Re: [SQL] Numeric and money In-reply-to: <01C07575.F26395D0.mdavis@sevainc.com> References: <01C07575.F26395D0.mdavis@sevainc.com> Comments: In-reply-to Michael Davis message dated "Wed, 03 Jan 2001 11:11:36 -0700" Date: Wed, 03 Jan 2001 15:36:49 -0500 Message-ID: <17683.978554209@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/89 X-Sequence-Number: 2255 [ mail lists trimmed to something a tad more reasonable ] Michael Davis writes: > From within Access, I can't update any table with a numeric data type > because of the "select * from tst where amount = 1.1;" failure. Yeah. The problem here is the conflict between interpreting '1.1' as a "float8" constant vs. interpreting it as a "numeric" constant. In order to fix this we need to settle on a better type promotion hierarchy among the various numeric datatypes. You can find past discussions of the issue in the pghackers archives. I made a proposal on 13-May-2000 that I think was objected to by some people, though I don't recall exactly why. regards, tom lane