Forum: Ruby Jruby precision issue with reading float values in mysql db

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
561319f16a08e221a31d13f4419a7de4?d=identicon&s=25 Pradeep Gatram (pradeepgatram)
on 2009-05-27 11:41
(Received via mailing list)
Hi,

I was trying to upgrade from 1.1.6 to 1.2.0 and noticed a strange
issue with floats. In Jruby 1.2.0, a float like 2.52342 is read as
2.52342009544373 from the DB.

A few steps to reproduce this.
1. Migration:     t.float :reading
2. Fixture:        reading: 2.52342
3. Run script/console

jruby script/console
Loading development environment (Rails 2.2.2)
>> Foo.first.reading
=> 2.52342009544373

Any idea if this has been logged as a bug or if there is a workaround?
561319f16a08e221a31d13f4419a7de4?d=identicon&s=25 Pradeep Gatram (pradeepgatram)
on 2009-05-28 08:36
(Received via mailing list)
The issue persists with both 1.3.0 RC1 & RC2.
Ede2aa10c6462f1d825143879be59e38?d=identicon&s=25 Charles Oliver Nutter (Guest)
on 2009-05-28 19:21
(Received via mailing list)
It seems the problem is that we're showing the actual machine precision
here. Floats are rarely 100% accurate, and this is likely a case where
it's losing some accuracy going into or coming out of the database. It's
possible there's a bug somewhere, but expecting floats to always be an
exact amount generally leads to bugs.

At any rate, can you file an issue for this in JRuby's bug tracker, and
if it's valid we'll try to fix it :)
This topic is locked and can not be replied to.