Received: from s20.highertech.net (root@s20.highertech.net [209.54.120.20]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA57530; Mon, 28 Jun 1999 15:43:31 -0400 (EDT) (envelope-from jt-kirkpatrick@mpsllc.com) Received: from kirkpatrickjt (whiteoak-34.highertech.net [209.140.56.34] (may be forged)) by s20.highertech.net (8.8.6/8.8.6) with SMTP id PAA17969; Mon, 28 Jun 1999 15:42:48 -0400 Received: by localhost with Microsoft MAPI; Mon, 28 Jun 1999 15:43:40 -0400 Message-ID: <01BEC17C.FE853200.jt-kirkpatrick@mpsllc.com> From: JT Kirkpatrick To: "'pgsql-admin@hub.org'" , "'pgsql-sql@hub.org'" Subject: float4 Date: Mon, 28 Jun 1999 15:43:37 -0400 Organization: MPS, LLC X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Encoding: 10 TEXT we have a database (linux, 6.4.2, new odbc, connections from msaccess / win98) -- access doesn't fully appreciate the monetary type in postgres, so we made all monetary fields FLOAT4's. weird stuff -- or maybe not to you -- we insert 23516.69 into a float4 field directly in psql, and then select it, and it shows 23516.7. this is not good for a field used for MONEY!!! what are the limitations of float4? should i have used float8? thanks for any help you can offer. . . jt