I doubt we'll be able to make the checksum queries compatible with ONLY_FULL_GROUP_BY. So we should at least document this requirement (i.e. no ONLY_FULL_GROUP_BY). We should probably also look into making the tool simply set the sql_mode it knows it needs. In this case, I can imagine why a user's server has ONLY_FULL_GROUP_BY on by default--to prevent people from abusing aggregate functions--but in our case we know we're correctly exploiting MySQL's extension to/flexibility with aggregate functions.
I doubt we'll be able to make the checksum queries compatible with ONLY_FULL_GROUP_BY. So we should at least document this requirement (i.e. no ONLY_FULL_ GROUP_BY) . We should probably also look into making the tool simply set the sql_mode it knows it needs. In this case, I can imagine why a user's server has ONLY_FULL_GROUP_BY on by default--to prevent people from abusing aggregate functions--but in our case we know we're correctly exploiting MySQL's extension to/flexibility with aggregate functions.