| Bug #70562 | SQLRowCount() returns wrong result after update with long data | ||
|---|---|---|---|
| Submitted: | 9 Oct 2013 13:04 | Modified: | 11 Nov 2013 6:37 |
| Reporter: | Dimitry Sibiryakov | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
| Version: | 5.2.5 | OS: | Windows |
| Assigned to: | Bogdan Degtyariov | CPU Architecture: | Any |
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
[1 Nov 2013 7:45]
Bogdan Degtyariov
[1 Nov 2013 10:04]
Bogdan Degtyariov
Test case version 2
Attachment: bug70562v2.c (text/plain), 5.91 KiB.
[3 Nov 2013 11:10]
Dimitry Sibiryakov
Modified test case. First row count is ok, second is wrong
Attachment: bug70562v3.c (text/plain), 6.77 KiB.
