From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
Cc: | "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, llonergan(at)greenplum(dot)com, sfrost(at)snowman(dot)net, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: New version of money type |
Date: | 2006-09-29 04:07:58 |
Message-ID: | 9633.1159502878@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> I think it's also important to protect for the possibility of a more
> complete (and probably incompatible) type in the future, such as one
> that stores what currency a value is in.
Well, such a type could be called "currency", "cash", "forex" or several
other possibilities, so I don't see any particular argument that "money"
has to be removed before something better can exist. The tightrope that
D'Arcy has to walk is different: improving "money" without making it so
incompatible as to break existing apps that use it.
> Hrm... does ANSI say anything about money types?
No.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | ITAGAKI Takahiro | 2006-09-29 04:15:06 | Re: Another idea for dealing with cmin/cmax |
Previous Message | Tom Lane | 2006-09-29 03:57:12 | Re: Stored procedure array limits |