| Bug #110016 | max_prepared_stmt_count exceeded and memory leak - OdbcCommand / Insert | ||
|---|---|---|---|
| Submitted: | 10 Feb 2023 5:16 | Modified: | 22 Jan 2024 13:03 |
| Reporter: | Terry Fenning | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
| Version: | 8.0.32 | OS: | Windows (Win 10 Pro - Ver 22H2) |
| Assigned to: | MySQL Verification Team | CPU Architecture: | x86 (64 bit odbc driver) |
| Tags: | ODBC Memory Leak max_prepared_stmt_count | ||
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
