2011-02-07 12:03:11.270404+00:00 https://api.launchpad.net/1.0/bugs/714419 https://api.launchpad.net/1.0/~philip-stoev https://api.launchpad.net/1.0/bugs/714419/linked_branches https://api.launchpad.net/1.0/bugs/714419/activity https://bugs.launchpad.net/bugs/714419 Philip Stoev Kristian Nielsen Won't Fix Undecided 2011-02-07 07:38:02.003429+00:00 bug Philip Stoev added bug attachment added Philip Stoev attachment added Philip Stoev maria: assignee Philip Stoev summary Philip Stoev maria: status Kristian Nielsen Philip Stoev Philip Stoev Philip Stoev Kristian Nielsen select col_double_key from table1_innodb; 1.21212121212121e+15 This output is not precise enough to distinguish the two different values on the master and cloned slave. In MySQL 5.5 they use a better library for printing floating-point numbers. Maybe that provides a textual decimal representation for mysqldump with sufficient precision, which could be the reason the bug is not reproducible there. I do not think we should fix this in 5.1/5.2. A work-around to get the RQG test to not fail could be to only use values for double columns which are integers with at most 14 digits, as I believe the textual decimal representation is precise for such numbers. ]]> LPexportBug714419_bug714419.zz LPexportBug714419_bug714419.yy