| Bug #93982 | Ways to retain Read-Locks for 'SELECT .. FOR UPDATE' across commit points | ||
|---|---|---|---|
| Submitted: | 18 Jan 2019 14:29 | Modified: | 22 Jan 2019 13:50 |
| Reporter: | Vibin Varghese | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Stored Routines | Severity: | S4 (Feature request) |
| Version: | 5.3.9 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Cursor Processing, For Update, Retain Read Lock across Commit Points | ||
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
