372

I want to store many records in a MySQL database. All of them contains money values. But I don't know how many digits will be inserted for each one.
Which data type do I have to use for this purpose?
VARCHAR or INT (or other numeric data types)?

Improve this question
2
  • 21
    deimal(10,2) is what i use ... you can adjust the values depending on size expected Commented Oct 23, 2012 at 12:27
  • 10
    Related question is Best Data Type for Currency ;). Commented Apr 28, 2015 at 10:10

14 Answers 14

Reset to default
506

Since money needs an exact representation don't use data types that are only approximate like float. You can use a fixed-point numeric data type for that like

decimal(15,2)
  • 15 is the precision (total length of value including decimal places)
  • 2 is the number of digits after decimal point
  • The max possible number in this example would be 9999999999999.99

See MySQL Numeric Types:

These types are used when it is important to preserve exact precision, for example with monetary data.

Improve this answer
Sign up to request clarification or add additional context in comments.

8 Comments

what could be the difference between decimal and numeric data type for this case?
In MySQL decimal and numeric are the same.
I personally use numeric(19,4) for financial records that gives you a better hand to play and adopt new requests easily.
I agree with YahyaE, more decimals is better. There are some currencies that typically use 3 decimal places, such as the Bahraini, Jordanian, or Kuwaiti Dinars, so you need at least 3. Four or five is better.
@EdwinHoogerbeets Not being an accountant... but running a small biz in the UK... I remember reading somewhere a long time ago that currency figures should be stored to 4 decimals even for £, $, etc. so that certain calculations might actually use the last 2 decimal places for certain obscure accounting contexts. Wd need an accountant to confirm/refute.
|
94

You can use DECIMAL or NUMERIC both are same

The DECIMAL and NUMERIC types store exact numeric data values. These types are used when it is important to preserve exact precision, for example with monetary data. In MySQL, NUMERIC is implemented as DECIMAL, so the following remarks about DECIMAL apply equally to NUMERIC. : MySQL

i.e. DECIMAL(10,2)

Example settings

Good read

Improve this answer

2 Comments

I am using decimal(10,2) for my money value, however when I put something like 867,000.00 it gets saved as 867. what am I doing wrong?
@codeinprogress you have a comma in your money value...if it goes into the database that same way. Mysql will truncate starting from the comma position
47

I prefer to use BIGINT, and store the values in by multiply with 100, so that it will become integer.

For e.g., to represent a currency value of 93.49, the value shall be stored as 9349, while displaying the value we can divide by 100 and display. This will occupy less storage space.

Caution:
Mostly we don't perform currency * currency multiplication, in case if we are doing it then divide the result with 100 and store, so that it returns to proper precision.

Improve this answer

9 Comments

I remember being told a similar thing by a professor on my Computer Systems university course. I was taught the most precise way is to store in pennies (or cent) by multiply by 100 and saving as an Integer and dividing by 100 to display it to the user. I guess this has benefits in terms of accuracy and performance of the database system.
What is the advantage over DECIMAL? You create a need to translate pennies to dollars, and woe if you forget it at some point.
Space is the only advantage, but yes we need to be more careful when we are using this feature.
In case it's not obvious: be wary of using the scale removing method if you store money in fractional cents (e.g., $0.005 or $0.12345) because they will not reduce to an integer after multiplying by 100. If you know the precision of the values it's clear the best option is to use DECIMAL. But if you don't know the precision (as in my examples) then…would FLOAT be appropriate?
An advantage of this method comes when using a language like JavaScript that uses IEEE-754 to store floating point numbers. This specification does not guarantee that 0.1 + 0.2 === 0.3 is true. Storing currency as an integer gives certainty that your application will not incur that kind of error. This may not be the best solution though. I arrived at this page while researching solutions and I'm not done yet.
|
29

It depends on your need.

Using DECIMAL(10,2) usually is enough but if you need a little bit more precise values you can set DECIMAL(10,4).

If you work with big values replace 10 with 19.

Improve this answer

3 Comments

I am using decimal(10,2) for my money value, however when I put something like 867,000.00 it gets saved as 867. what am I doing wrong?
@codeinprogress Using the wrong locale/decimal separator?
@codeinprogress You are using the , for digit grouping. Do not do that. Never use comma or point for digit grouping.
19

If your application needs to handle money values up to a trillion then this should work: 13,2 If you need to comply with GAAP (Generally Accepted Accounting Principles) then use: 13,4

Usually you should sum your money values at 13,4 before rounding of the output to 13,2.

Improve this answer

4 Comments

If you're going to take Bitcoin, you're going to need 8 decimal places, although most wallets go to mBTC which is 3 en.wikipedia.org/wiki/Bitcoin
Don't think this answer is true. opendata.stackexchange.com/a/10348/13983 @david.ee got a source for that?
@EvanCarroll let me answer for david.ee. I think this article may be the source rietta.com/blog/2012/03/03/best-data-types-for-currencymoney-in
@naXa the link does not quote anything from any source that support's the claim of using 13,4 for GAAP. All you did was link to an article that makes the same unsubstantiated claim.
14

At the time this question was asked nobody thought about Bitcoin price. In the case of BTC, it is probably insufficient to use DECIMAL(15,2). If the Bitcoin will rise to $100,000 or more, we will need at least DECIMAL(18,9) to support cryptocurrencies in our apps.

DECIMAL(18,9) takes 8 bytes of space in MySQL (4 bytes per 9 digits).

Improve this answer

4 Comments

> A bitcoin can be divided down to 8 decimal places. Therefore, 0.00000001 BTC is the smallest amount that can be handled in a transaction. I think you mean 8 instead of 9?
I know, but 9 takes the same disk space as 8. From MySQL docs: "Values for DECIMAL columns are stored using a binary format that packs nine decimal digits into 4 bytes"
Actually DECIMAL(18,9) takes 8 bytes, not 12. See this.
Yes, you are right @at54321
13

We use double.

*gasp*

Why?

Because it can represent any 15 digit number with no constraints on where the decimal point is. All for a measly 8 bytes!

So it can represent:

  • 0.123456789012345
  • 123456789012345.0

...and anything in between.

This is useful because we're dealing with global currencies, and double can store the various numbers of decimal places we'll likely encounter.

A single double field can represent 999,999,999,999,999s in Japanese yens, 9,999,999,999,999.99s in US dollars and even 9,999,999.99999999s in bitcoins

If you try doing the same with decimal, you need decimal(30, 15) which costs 14 bytes.

Caveats

Of course, using double isn't without caveats.

However, it's not loss of accuracy as some tend to point out. Even though double itself may not be internally exact to the base 10 system, we can make it exact by rounding the value we pull from the database to its significant decimal places. If needed that is. (e.g. If it's going to be outputted, and base 10 representation is required.)

The caveats are, any time we perform arithmetic with it, we need to normalize the result (by rounding it to its significant decimal places) before:

  1. Performing comparisons on it.
  2. Writing it back to the database.

Another kind of caveat is, unlike decimal(m, d) where the database will prevent programs from inserting a number with more than m digits, no such validations exists with double. A program could insert a user inputted value of 20 digits and it'll end up being silently recorded as an inaccurate amount.

Improve this answer

7 Comments

First time I've seen an answer like this, interesting. Q: If I write a float like 1.41 to the database and for some reason I need to multiply it by some huge number in mysql, like 1.000.000.000.000. Will the rounded result exactly be: 1.410.000.000.000?
@roelleor For the result to be exactly 1,410,000,000,000 (comma as thousands separator) the input is assumed to be 1.410000000000 (twelve significant decimal places), but multiplying that by 1,000,000,000,000 (which is 13 significant digits left of decimal point) means we are working with at least a combined 25 digits of significance. This far surpasses the 15 available for a double, so design-wise I think it would be very broken.
Then you sum up the total cost of buying 3 items with a cost of 0.99 each, and end up with a total sum of 2.9699999999999998.
@ChristofferHammarström 2.9699999999999998 is way more than 15 digits. You need to know how many digits are significant your currency and round to it. If it's the full 15, it's going to be 2.97000000000000, but you started on 0.99 so it's probably two so 2.97. For details, see under caveats.
So you can either remember to always round and hope that you don't have enough compounded errors, or you can use a data type which doesn't have the problem.
|
8

If GAAP Compliance is required or you need 4 decimal places:

DECIMAL(13, 4) Which supports a max value of:

$999,999,999.9999

Otherwise, if 2 decimal places is enough: DECIMAL(13,2)

src: https://rietta.com/blog/best-data-types-for-currencymoney-in/

Improve this answer

Comments

5

Indeed this relies on the programmer's preferences. I personally use: numeric(15,4) to conform to the Generally Accepted Accounting Principles (GAAP).

Improve this answer

1 Comment

It has nothing whatsoever to do with "programmer's preferences" or what you 'personally use'. It is dictated by the problem domain, which requires a decimal radix. This is not a matter in which the programmer gets to exercise his own personal preferences.
5

Storing money as BIGINT multiplied by 100 or more with the reason to use less storage space makes no sense in all "normal" situations.

Improve this answer

Comments

4

Try using

Decimal(19,4)

this usually works with every other DB as well

Improve this answer

Comments

2

Use DECIMAL (or NUMERIC - it's the same in MySQL).

Do NOT use DOUBLE or FLOAT (especially FLOAT). Those are floating-point numbers with binary precision. (In Oracle, the NUMBER type is also a floating-point but with decimal precision, which is fine for monetary operations).

With DECIMAL you need to specify the total precision and the fractional part. For example:

  • DECIMAL(10,2) can store values between -99,999,999.99 and 99,999,999.99.
  • DECIMAL(19,4) can store values between -999,999,999,999,999.9999 and 999,999,999,999,999.9999.

Choose a range that will be big enough for your case, but be aware that the bigger the range, the more storage would be used. In MySQL, DECIMAL(10,2) will always use 5 bytes and DECIMAL(19,4) will always use 9 bytes, regardless of the actual values you store. See this for more on how DECIMAL's storage size is calculated.

Improve this answer

Comments

1

There are 2 valid options:

  1. use integer amount of currency minor units (e.g. cents)
  2. represent amount as decimal value of the currency

In both cases you should use decimal data type to have enough significant digits. The difference can be in precision:

  • even for integer amount of minor units it's better to have extra precisions for accumulators (account for accumulating 10% fees from 1-cent operations)
  • different currencies have different number of decimals, cryptocurrencies have up to 18 decimals
  • The number of decimals can change over time due to inflation

Source and more caveats and facts.

Improve this answer

Comments

0

Multiplies 10000 and stores as BIGINT, like "Currency" in Visual Basic and Office. See https://msdn.microsoft.com/en-us/library/office/gg264338.aspx

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.