Re: [HACKERS] GSoC 2017 - Mailing list pgsql-hackers

From Brad DeJong
Subject Re: [HACKERS] GSoC 2017
Date
Msg-id CY1PR0201MB1897A4658BED15744EF40488FF760@CY1PR0201MB1897.namprd02.prod.outlook.com
Whole thread Raw
In response to Re: [HACKERS] GSoC 2017  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] GSoC 2017  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On January 27, 2017 07:08, Tom Lane wrote:
> ... The things I think are unique to the currency situation are: ...

Add the potential for regulatory requirements to change at any time - sort of like timezone information. So no hard
codedbehavior.   rounding method/accuracy   storage precision different than display precision   conversion method
(multiply,divide, triangulate, other)   use of spot rates (multiple rate sources) rather than/in addition to
time-varyingrates 

responding to the overall idea of a currency type

Numeric values with units so that you get a warning/error when you mix different units in calculations? Ability to
specifyrounding methods and intermediate precisions for calculations? 
+1 Good ideas with lots of potential applications.

Built-in currency type?
-1 I suspect this is one of those things that seems like a good idea but really isn't.



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] pg_background contrib module proposal
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] pg_ls_dir & friends still have a hard-coded superuser check