| Bug #28887 | SQLBIGINT is assumed to be a long long | ||
|---|---|---|---|
| Submitted: | 4 Jun 2007 22:27 | Modified: | 13 Mar 2014 11:05 |
| Reporter: | Jim Winstead | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
| Version: | 5.2 | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | 64-bit, SQLBIGINT | ||
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
