well, it appears that you are quite correct. changing the column
definition to float(11,3) for example now does the correct thing.
sean c peters wrote:
> This is not a bug, its behaving exactly as it should. When you specify a
> float(11,9) - you're saying an 11 digit number where 9 are after the decimal,
> so only 2 digits are allowed before the decimal.
> sean peters
> On Thursday 05 August 2004 15:47, Jeff Mathis wrote:
>>after lokking at this, it appears that our float(11,9) columns cannot
>>store an number larger than 100 or smaller than -100. the database is
>>rounding the number! If we insert numbers -100 < x < 100, then its fine.
>>is there a configuration setting somewhere, or is this a known bug?
>>Jeff Mathis wrote:
>>>after upgrading from 4.0.4 to 4.1.3, we noticed that some of our
>>>float(11,9) columns refused to store anything other than the numer -100
>>>or the number 100, even though the insert or update sql clearly
>>>specifies other numbers. We've tried dropping the table and reloading
>>>the data -- same problem. we're using Connector/J to load the data.
>>>is this a know issue?
>>Jeff Mathis, Ph.D. 505-955-1434
>>Prediction Company jmathis@stripped
>>525 Camino de los Marquez, Ste 6 http://www.predict.com
>>Santa Fe, NM 87505
Jeff Mathis, Ph.D. 505-955-1434
Prediction Company jmathis@stripped
525 Camino de los Marquez, Ste 6 http://www.predict.com
Santa Fe, NM 87505