| Bug #121166 | concurrent updates make FK ON UPDATE CASCADE miss child rows | ||
|---|---|---|---|
| Submitted: | 25 Aug 1:41 | ||
| Reporter: | yewei Xu (OCA) | Email Updates: | |
| Status: | Open | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
| Version: | 8.0.30 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | cascade, data-integrity, foreign-key, gap-lock, innodb, READ-COMMITTED, replication | ||
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[25 Aug 1:43]
yewei Xu
[25 Aug 1:43]
yewei Xu
result file for testcase
Attachment: fk_cascade_miss_child_rows.result (application/octet-stream, text), 3.00 KiB.
