P: n/a

What do people recommend for storing money amounts? I've seen people use
NUMERIC(18,3) and other use NUMERIC(18,4). Which one is more appropriate
and why? This is considering various existing currencies, some having
low rates (like IDR, in which you can have large amount up to hundreds
of trillions) and some high rates (like USD, in which you can have small
amount like 0.1 cent). Are there places/industries which involve values
lower than 0.1 cent?
And what about 'factor' field in currency conversion table? Should I use
REAL, or DOUBLE PRECISION (do we need 1516 digit precision?) or NUMERIC
(exact numbers). The factor should range between 1E3 (e.g. converting
IDR to USD) to 1E4 (e.g. converting IDR to pounds/euros).

dave
(end of broadcast)
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org  
Share this Question
P: n/a

On Wed, 20031203 at 07:02, David Garamond wrote: What do people recommend for storing money amounts? I've seen people use NUMERIC(18,3) and other use NUMERIC(18,4). Which one is more appropriate and why? This is considering various existing currencies, some having low rates (like IDR, in which you can have large amount up to hundreds of trillions) and some high rates (like USD, in which you can have small amount like 0.1 cent). Are there places/industries which involve values lower than 0.1 cent?
I think you should match the customer's data and use whatever precision
is necessary for it. The needs of a small shop will not be the same as a
currency trader's.
You should not regard amounts in different currencies as equivalent.
You cannot add Euros to dollars and get a meaningful figure; so they
should not be in the same column. If you are handling multiple
currencies, your database design needs to be a lot more sophisticated
than having a single money column.
And what about 'factor' field in currency conversion table? Should I use REAL, or DOUBLE PRECISION (do we need 1516 digit precision?) or NUMERIC (exact numbers). The factor should range between 1E3 (e.g. converting IDR to USD) to 1E4 (e.g. converting IDR to pounds/euros).
You should only use NUMERIC for money; any kind of floating point
representation will lose detail somewhere along the line. (I suppose
you could use BIGINT for Japanese Yen.)

Oliver Elphick Ol************@lfix.co.uk
Isle of Wight, UK http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
"What shall we then say to these things? If God be for
us, who can be against us?" Romans 8:31
(end of broadcast)
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match  
P: n/a

Oliver Elphick wrote: You should not regard amounts in different currencies as equivalent. You cannot add Euros to dollars and get a meaningful figure; so they should not be in the same column.
I plan to store amount in a column (NUMERIC) and currency id in another
(CHAR(3)). Plus another column for amount in 'standard' currency (e.g.
USD; all addition/sum will be done to this column).
You should only use NUMERIC for money; any kind of floating point representation will lose detail somewhere along the line. (I suppose you could use BIGINT for Japanese Yen.)

dave
(end of broadcast)
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribenomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly  
P: n/a

Funny you mention IDR I happen to be in Jakarta at the moment.
Obviously different customers have different requirements, but I always
suggest trading performance for usefulness where necessary.
Obviously, the scale will need to be in accordance with the needs of your
customer (unlikey to need any for IDR; 2, 3, or more depending on industry
for USD). I would also always suggest overshooting the precision by a few
places to ensure that:
1) if there is another banking crisis, your app still performs
2) take into account future inflation
3) take into account future growth.
Best WIshes,
Chris Travers
(end of broadcast)
TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html  
P: n/a

David Garamond wrote: I plan to store amount in a column (NUMERIC) and currency id in another (CHAR(3)). Plus another column for amount in 'standard' currency (e.g. USD; all addition/sum will be done to this column).
If your system really is going to handle multiple, simultaneous currencies,
beware of constant changes in the exchange rate between them. Probably
you'll be better by never storing anything in a 'standard currency' column
and doing instead all math on the fly, referring to a separate
'exchange_rates' table when needed (i.e. always :). Of course, all of this
has nothing to do with the technical solution but instead with the bussiness
rules the application must follow, so they must be incorporated early at the
spec level. In the end, probably an accountant will be the most qualified
one to define these things.
With regard to precision, it is common in certain applications the need to
handle very small amounts, especially when used as factors of a larger
calculation. I've even seen once some rates defined in hundredths of cents!
hth
cl.
(end of broadcast)
TIP 8: explain analyze is your friend  
P: n/a

Martha Stewart called it a Good Thing when cl******@hotmail.com ("Claudio Lapidus") wrote: With regard to precision, it is common in certain applications the need to handle very small amounts, especially when used as factors of a larger calculation. I've even seen once some rates defined in hundredths of cents!
Well, you don't need terribly much precision in the currency exchange
rate if the amount being converted is small. You only need a couple
significant digits to convert $0.24 USD to the appropriate amount in
$CDN.
But to get the pennies right on a $10,000 USD transaction converted
into GBP (UK Pounds), you need all the official precision that there
is. And if your calculation is off by 4 cents, some of those
accounting folk are liable to thrash you mercilessly over it. If you
get calculations WRONG, they get really uncomfortable, and want to
know why.

(reverse (concatenate 'string "ac.notelrac.teneerf" "@" "454aa")) http://www3.sympatico.ca/cbbrowne/li...ributions.html
"Women who seek to be equal to men lack ambition. "
 Timothy Leary  
P: n/a

"Claudio Lapidus" <cl******@hotmail.com> writes: With regard to precision, it is common in certain applications the need to handle very small amounts, especially when used as factors of a larger calculation. I've even seen once some rates defined in hundredths of cents!
Normally there's nothing smaller than a tenth of a cent in US currency. It's
called a "mill". (or "mil"? I forget.). Of course you have to multiply
currency amounts by floating point numbers like interest rates or such, and
that will produce strange numbers but they'll always be rounded off to at
least mills and usually cents. You never actually debit or credit partial
mills.
At least that's how I was taught it was supposed to work.
I'm sure someone somewhere isn't following it.

greg
(end of broadcast)
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribenomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly  
P: n/a

Christopher Browne wrote: But to get the pennies right on a $10,000 USD transaction converted into GBP (UK Pounds), you need all the official precision that there is. And if your calculation is off by 4 cents, some of those accounting folk are liable to thrash you mercilessly over it. If you get calculations WRONG, they get really uncomfortable, and want to know why.
What I have done is store the currency amounts as bigints, at the same
precision defined for the currency (ie cents for dollars, pence for
pounds, etc). This guarantees that you don't get any rounding errors
when storing the figures as a floating point type. When manipulating the
numbers, I use Java BigDecimals, which don't lose any precision either,
and convert back to bigints to store in the database.
YMMV.
Regards,
Graham

(end of broadcast)
TIP 6: Have you searched our list archives? http://archives.postgresql.org  
P: n/a

Graham Leggett wrote: Christopher Browne wrote:
But to get the pennies right on a $10,000 USD transaction converted into GBP (UK Pounds), you need all the official precision that there is. And if your calculation is off by 4 cents, some of those accounting folk are liable to thrash you mercilessly over it. If you get calculations WRONG, they get really uncomfortable, and want to know why.
What I have done is store the currency amounts as bigints, at the same precision defined for the currency (ie cents for dollars, pence for pounds, etc). This guarantees that you don't get any rounding errors when storing the figures as a floating point type. When manipulating the numbers, I use Java BigDecimals, which don't lose any precision either, and convert back to bigints to store in the database.
You won't get any rounding errors in NUMERIC either. What people should
be concerned of is to find an arbitrary precision package for the
frontend programming language they're using.
Jan

#================================================= =====================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule  forgive me. #
#================================================= = Ja******@Yahoo.com #
(end of broadcast)
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org  
P: n/a

On Thu, 4 Dec 2003, Jan Wieck wrote: Graham Leggett wrote:
Christopher Browne wrote:
What I have done is store the currency amounts as bigints, at the same precision defined for the currency (ie cents for dollars, pence for pounds, etc). This guarantees that you don't get any rounding errors when storing the figures as a floating point type. When manipulating the numbers, I use Java BigDecimals, which don't lose any precision either, and convert back to bigints to store in the database.
You won't get any rounding errors in NUMERIC either. What people should be concerned of is to find an arbitrary precision package for the frontend programming language they're using.
I agree, I use BigDecimal's in Java, and NUMERIC's in PostgreSQL, they
seem like a perfect match. Floating point numbers are not suitable for
money in my opinion.
(end of broadcast)
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)  
P: n/a

Jan Wieck wrote: You won't get any rounding errors in NUMERIC either. What people should be concerned of is to find an arbitrary precision package for the frontend programming language they're using.
What is the definition of a numeric number? I understand (from studying
numeric methods all those years ago) that the base 10 decimal number 0.1
cannot be stored exactly in base 2 floating point, thus my use of
integers  is numeric an arbitrary precision concept?
Regards,
Graham

(end of broadcast)
TIP 8: explain analyze is your friend  
P: n/a

It's probably in the documentation, but numeric is stored as a string of
digits (or was it mibbles). In any case, if you wanted to list the weight of
the earth to 20 decimal places, numeric is for you. If you like you can
consider it integer arithmatic except the scaling is handled for you.
The format is NUMERIC(x,y) where x is the total number of digits and y is
the number of decimal places. There are rules about the results of
multiplication and division and such.
Hope this helps,
On Fri, Dec 05, 2003 at 02:39:42PM +0200, Graham Leggett wrote: Jan Wieck wrote: You won't get any rounding errors in NUMERIC either. What people should be concerned of is to find an arbitrary precision package for the frontend programming language they're using. What is the definition of a numeric number? I understand (from studying numeric methods all those years ago) that the base 10 decimal number 0.1 cannot be stored exactly in base 2 floating point, thus my use of integers  is numeric an arbitrary precision concept? Regards, Graham  (end of broadcast) TIP 8: explain analyze is your friend

Martijn van Oosterhout <kl*****@svana.org> http://svana.org/kleptog/ "All that is needed for the forces of evil to triumph is for enough good men to do nothing."  Edmond Burke "The penalty good people pay for not being interested in politics is to be governed by people worse than themselves."  Plato
BEGIN PGP SIGNATURE
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE/0H6/Y5Twig3Ge+YRAqHqAJ9rB5VWdXEvTg+/e5/rfeMD5IOiowCfeK5f
aBz+h6AkfQdep888hdxkuTw=
=dxy7
END PGP SIGNATURE  
P: n/a

Graham Leggett wrote: Jan Wieck wrote:
You won't get any rounding errors in NUMERIC either. What people should be concerned of is to find an arbitrary precision package for the frontend programming language they're using.
What is the definition of a numeric number? I understand (from studying numeric methods all those years ago) that the base 10 decimal number 0.1 cannot be stored exactly in base 2 floating point, thus my use of integers  is numeric an arbitrary precision concept?
The PostgreSQL datatype NUMERIC is performing decimal arithmetic. The
original I wrote used to do it string based, with one digit per byte but
stored the number as some sort of BCD, one digit per nibble. Tom Lane
changed that a while back into base 10,000 storage and calculation,
which has the advantages of doing 4 digits per loop and no need to
convert back and forth between the storage and the computational
representation.
Jan

#================================================= =====================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule  forgive me. #
#================================================= = Ja******@Yahoo.com #
(end of broadcast)
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)   This discussion thread is closed Replies have been disabled for this discussion.   Question stats  viewed: 17183
 replies: 12
 date asked: Nov 12 '05
