From: | "Igal (at) Lucee(dot)org" <igal(at)lucee(dot)org> |
---|---|
To: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Migrating money column from MS SQL Server to Postgres |
Date: | 2017-11-09 06:58:04 |
Message-ID: | 724bab58-87d9-7b02-867b-5d98b93aac7d@lucee.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/8/2017 6:25 PM, Igal @ Lucee.org wrote:
> On 11/8/2017 5:27 PM, Allan Kamau wrote:
>> Maybe using NUMERIC without explicitly stating the precision is
>> recommended. This would allow for values with many decimal places to
>> be accepted without truncation. Your field may need to capture very
>> small values such as those in bitcoin trading or some banking fee or
>> interest.
>
> That's a very good idea. For some reason I thought that I tried that
> earlier and it didn't work as expected, but I just tested it (again?)
> and it seems to work well, so that's what I'll do.
Another weird thing that I noticed:
On another column, "total_charged", that was migrated properly as a
`money` type, when I run `sum(total_charged::money)` I get `null`, but
if I cast it to numeric, i.e. `sum(total_charged::numeric)`, I get the
expected sum result.
Is there a logical explanation to that?
Igal
From | Date | Subject | |
---|---|---|---|
Next Message | Shreeyansh Dba | 2017-11-09 07:45:38 | Re: Can master and slave on different PG versions? |
Previous Message | Igal @ Lucee.org | 2017-11-09 02:25:24 | Re: Migrating money column from MS SQL Server to Postgres |