Received: from golem.jpl.nasa.gov (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.1/8.9.1) with ESMTP id AAA09646 for ; Fri, 1 Jan 1999 00:29:25 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost [127.0.0.1]) by golem.jpl.nasa.gov (8.8.5/8.8.5) with ESMTP id FAA08682; Fri, 1 Jan 1999 05:29:11 GMT Sender: tgl@mythos.jpl.nasa.gov Message-ID: <368C5D27.596E1AC5@alumni.caltech.edu> Date: Fri, 01 Jan 1999 05:29:11 +0000 From: "Thomas G. Lockhart" Organization: Caltech/JPL X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.30 i686) MIME-Version: 1.0 To: "Ken J. Wright" CC: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] Money type mapping to VB5 Jet workspace References: <3.0.32.19981231135827.00796e40@ori-ind.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > This is also a problem with the BDE & also with libpq. The odbc driver > could/should? fix this, but then what about libpq? The docs say the > money type is going away someday. Should we avoid using it? I believe > a proper fix involves both the backend & frontends. Forcing quotes > around a numeric value throws everyone off. Developer comments? We are just getting a NUMERIC() type implemented now by Jan Wieck. We haven't had a chance to try it out yet, but Jan is one of our best developers so it is likely to be a good replacement for the less general money type. It isn't yet certain that the very first implementation of NUMERIC() will allow one to omit the single quotes around values, but it probably will. Barring unforeseen problems, it should be available for v6.5. - Tom