Re: type money causes unrestorable dump - Mailing list pgsql-hackers

From D'Arcy J.M. Cain
Subject Re: type money causes unrestorable dump
Date
Msg-id 20071009112616.2aeb164a.darcy@druid.net
Whole thread Raw
In response to Re: type money causes unrestorable dump  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: type money causes unrestorable dump  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: type money causes unrestorable dump  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
On Mon, 8 Oct 2007 20:02:56 -0700
"Joshua D. Drake" <jd@commandprompt.com> wrote:
> The money data type has been deprecated for years. It is completely non
> standard and essentially duplicative of numeric/decimal. What is the
> point?

It may be deprecated (maybe not) and it may have drawbacks but it is
not a duplication of numeric or decimal.  While numeric/decimal may be
faster for I/O, money is faster for doing large sums.  Depending on
your needs it does have an advantage over numeric.

That said, I wonder if there is another answer to this question.
Perhaps the functions in cash.c can be pulled out and made into
external functions that can be fed an int (long) and output the desired
format.  That way we could use the existing int or long type but
convert manually on I/O.  Let people choose whether they want the
simplification of the money type or the standardization allowed by just
using the functions.

Just a thought.

-- 
D'Arcy J.M. Cain <darcy@druid.net>         |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Including Snapshot Info with Indexes
Next
From: Andrew Dunstan
Date:
Subject: Re: ECPG regression tests