On 24 January 2017 at 03:42, Peter van Hardenberg <p...@pvh.ca> wrote: > The basic concept is that the value of a currency type is that it would > allow you to operate in multiple currencies without accidentally adding > them. You'd flatten them to a single type if when and how you wanted for any > given operation but could work without fear of losing information.
I don't think this even needs to be tied to currencies. I've often thought this would be generally useful for any value with units. This would prevent you from accidentally adding miles to kilometers or hours to parsecs which is just as valid as preventing you from adding CAD to USD. Then you could imagine having a few entirely optional helper functions that could automatically provide conversion factors using units.dat or currency exchange rates. But even if you don't use these helper functions they would still be useful. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
