Re: Constrainting NUMBER

Hi!

DA Morgan wrote:

> Lets say the column holds person's ages. Is there any value in
> NUMBER(4)?
Storing an age in a column is a very stupid idea. Do you really want to run a batch job at midnight updating the age from the birthday? When is midnight if your application is accessed from different time zones?

OTOH NUMBER(4) should work pretty well for trees ...

> How about money? Is there any value in allowing more
> than two decimal points? ...

There is one currency with 3 decimals (somewhere in the ME region). Most currencies have 2 decimals, the number of currencies with 0 decimals have decreased within the last few years (e.g Italy, Poland). Or think of the old UK system with Shillings ...

If you create an application that does not work in some tiny little kingdom on the Persian Gulf you might think: Just forget about this 0.0x % of the world.
But all the large international businesses with subsidiaries over there will tell you to get lost if it does not work everywhere.

brgds

-- 
Gunter Herrmann
Naples, Florida, USA