Re: Dealing with multiple currencies with the money type?

From: Simon Connah <simon(dot)n(dot)connah(at)protonmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-novice(at)lists(dot)postgresql(dot)org" <pgsql-novice(at)lists(dot)postgresql(dot)org>
Subject: Re: Dealing with multiple currencies with the money type?
Date: 2021-04-18 19:07:46
Message-ID: N2WLSjv6ynDZ36XnsCN8BxorUorgtXYSeDL7cNvVWXAS0ohKG3T3TYZXUW97Ds9bRZolw0UPl6mkenmUUs_Yw-c03kz24tvp86vdLD5iihw=@protonmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, April 18th, 2021 at 16:21, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Sunday, April 18, 2021, Simon Connah <simon(dot)n(dot)connah(at)protonmail(dot)com> wrote:
>

> > Hi,
> >

> > I've read this page:
> >

> > https://www.postgresql.org/docs/13/datatype-money.html
> >

> > which seems to suggest that lc_monetary dictates what currency the database uses for the money type. But what if you want to have transactions in USD, GBP and EUR from a database with en_GB.UTF8 locale?
> >

> > Is this possible?
>

> The money type should largely be avoided.  I find it useful for parsing external data but in the end store money using numeric.  Add a currency type field if you need to be explixit about what units the currency is in.
>

> David J.

Thank you.

OK I'll use numeric in that case.

Simon.

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Stephen Carboni 2021-04-21 12:13:19 Why is there no ADD CONSTRAINT IF NOT EXISTS ?
Previous Message David G. Johnston 2021-04-18 15:21:41 Re: Dealing with multiple currencies with the money type?