Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.11.12
-
None
-
None
-
None
-
linux
Description
Having a master/slave setup with aria tables
e.g.
CREATE TABLE `qmUploadFiles` ( |
`Tool` varchar(200) NOT NULL DEFAULT '', |
`Ref1` int(10) unsigned NOT NULL, |
`Ref2` int(10) unsigned NOT NULL, |
`Field` varchar(20) NOT NULL DEFAULT '', |
`Path` tinytext NOT NULL, |
`File` tinytext NOT NULL DEFAULT '', |
`ParentID` int(10) unsigned NOT NULL DEFAULT 0, |
`Date` datetime NOT NULL DEFAULT current_timestamp(), |
`hash` binary(20) DEFAULT NULL, |
`FileSize` int(10) unsigned NOT NULL DEFAULT 0, |
PRIMARY KEY (`Tool`,`Field`,`Ref1`,`Ref2`), |
) ENGINE=Aria DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_unicode_ci CHECKSUM=1 PAGE_CHECKSUM=1 |
often has different checksums if compared with quick algorithm.The extended (very slow) algorithm is correct.
Attachments
Issue Links
- relates to
-
MDEV-28020 CHECKSUM TABLE calculates different checksums
-
- Closed
-