| From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mike Mascari <mascarm(at)mascari(dot)com>, Mahmoud Taghizadeh <m_taghi(at)yahoo(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: monetary bug |
| Date: | 2004-08-23 04:49:33 |
| Message-ID: | Pine.LNX.4.44.0408230644180.9559-100000@zigo.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 22 Aug 2004, Peter Eisentraut wrote:
> To me, this seems completely wrong-headed. Data types should be defined
> by what operations you can do on them, not by what output format they
> have.
I totally agree, lets get rid of money all together.
If not, what makes money so special? Do we want other numeric types like
hexnumber, octalnamber, weight, length, ... All of these are different
ways to format a number in a user interface.
Of course one could imaging a system with units, so that if you multiplty
two lengths (meter) you get an area (meter^2) and so on.. But it's just
going to be complicated and no other programming language I know of have
gone that way.
--
/Dennis Björklund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2004-08-23 04:56:58 | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
| Previous Message | Tom Lane | 2004-08-23 04:28:48 | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |