| Bug #32420 | Don't cache results and SQLExtendedFetch work badly together | ||
|---|---|---|---|
| Submitted: | 15 Nov 2007 19:12 | Modified: | 14 Mar 2008 18:42 |
| Reporter: | Bogdan Degtyariov | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S2 (Serious) |
| Version: | 3.51.21 | OS: | Windows |
| Assigned to: | Jess Balint | CPU Architecture: | Any |
| Tags: | MSSQL, SQL_ROWSET_SIZE, SQLExtendedFetch | ||
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 Dec 2007 12:55]
Bogdan Degtyariov
[26 Dec 2007 19:55]
Bogdan Degtyariov
patch with the test case
Attachment: patch32240.diff (application/octet-stream, text), 11.06 KiB.
[23 Feb 2008 23:02]
Jess Balint
fix + test
Attachment: bug32420.diff (application/octet-stream, text), 4.42 KiB.
