So no one can help then..... I'll be submitting a bug report then. Thanks all. http://bugs.mysql.com/bug.php?id=28121
Yeah, it's simply a quirk of MySQL 5, Ruby. I wonder why they decided to change it? I mean, it's not only with MySQL 5 itself but in the documentation too!
Yes i dunno but it has literally screwed up one of my biggest applications. I had to roll back to version 4 and have a separate dedicated machine just for a couple of databases.
As i don't run mysql5 i can't check this out. But maybe the stupid mysql cast the number to an decimal or whatever before insert because of missing ".0"
I know this is a really old thread, but what is the solution for handling very large numbers like the OP? I also have an online game, and the in game currency for players and groups are reaching the limitations. I don't know how to get around this? I've had my fields set as BigINT unsigned, but that's not enough.
Are Ruby and I the only people who have ever had this issue? It's affecting my game because players can't deposit their game cash, it just disappears once they reach this limit.
If you want a solution for storing numbers larger than 65 digits in MySQL 5, there isn't one. You can store them as text and convert going in and coming out, or you can use a database that handles larger numbers.
According to the original bug report stated by the OP, this bug has been fixed in 5.0.44 and 5.1.20 up. Not sure if related, just pointing out.