Could binary charset in percona.checksums be possible workaround?
CREATE TABLE `checksums` ( `db` binary(64) NOT NULL, `tbl` binary(64) NOT NULL, `chunk` int(11) NOT NULL, `chunk_time` float DEFAULT NULL, `chunk_index` varbinary(200) DEFAULT NULL, `lower_boundary` blob, `upper_boundary` blob, `this_crc` binary(40) NOT NULL, `this_cnt` int(11) NOT NULL, `master_crc` binary(40) DEFAULT NULL, `master_cnt` int(11) DEFAULT NULL, `ts` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`db`,`tbl`,`chunk`), KEY `ts_db_tbl` (`ts`,`db`,`tbl`) ) ENGINE=InnoDB DEFAULT CHARSET=binary
Could binary charset in percona.checksums be possible workaround?
CREATE TABLE `checksums` ( tbl`,`chunk` ),
`db` binary(64) NOT NULL,
`tbl` binary(64) NOT NULL,
`chunk` int(11) NOT NULL,
`chunk_time` float DEFAULT NULL,
`chunk_index` varbinary(200) DEFAULT NULL,
`lower_boundary` blob,
`upper_boundary` blob,
`this_crc` binary(40) NOT NULL,
`this_cnt` int(11) NOT NULL,
`master_crc` binary(40) DEFAULT NULL,
`master_cnt` int(11) DEFAULT NULL,
`ts` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`db`,`
KEY `ts_db_tbl` (`ts`,`db`,`tbl`)
) ENGINE=InnoDB DEFAULT CHARSET=binary