What is "12.5" value?
Where you've got it from?
It's a result of either some measurement or some calculation (of values measured) stored with some precision you cannot change and have to accept.
So, if "12.5" stored in money datatipe field tells you that the real value is between 12.5000(0) and 12.5000(9).
Storing it in DECIMAL(3, 1) field you decrease its precision, because money value 12.5123 will end up in exactly the same DECIMAL(3, 1) value as 12.5421 or 12.5252.
So, you cannot use assumption of "implied zeros" as some "brilliant minds" suggested here.
> Are you saying that some numeric values cannot be stored precisely, or are you saying that *all* numeric values cannot be stored precisely?
You probebly did not read the whole topic. Because I answered on this question at least 3 times.
OK, it's Saturday here, so I can afford to repeat it again and not to force you to go through this.
There is 1 value which is represented by 12.5000 precisely: it's 12.5000(0).
There is infinite number of values which are represented by 12.5000 not precisely: > 12.5000(0) and < 12.5001(0).
The probability of the actual value (which don't have a chance to know) is represented by 12.5000 precisely equals 1/infinity = 0.
"Probablity = 0" means "it's impossible".
If it's impossible event when numeric value is stored precisely then all numeric values cannot be stored precisely.
Any objection to this logic?