At 4:49 PM +0300 8/14/99, Tonu Samuel wrote:
>> I request that the developers of MySQL implement some sort of special type
>> of field that can be used to store currency up to 4 digits precision
>> (specified in field definition) exactly, using a BIGINT shifted a number of
>> digits, so that it doesn't have to be stored unpacked and thus things like
>> Sum() or ORDER BY go
>> faster. (I assume when you order by or sum an unpacked decimal field you
>> have to make a billion calls to strtol). This saves the trouble of having to
>> do a billion *100, /100 in SQL statements, thanks.
> But why the other type like DECIMAL or FLOAT don't work for you?
I suspect he's thinking along the lines that since DECIMAL is represented
as a string, it's less efficient to deal with than a type represented
numerically, and that FLOAT is subject to rounding error.
Can you address the question in terms of these concerns?
Paul DuBois, paul@stripped