Bug #53235 SQLColumns returns wrong transfer octet length and display size for DECIMAL
| Submitted: | 28 Apr 2010 6:29 | Modified: | 30 Jun 2010 9:35 |
|---|---|---|---|
| Reporter: | Bogdan Degtyariov | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S2 (Serious) |
| Version: | 5.1.6 | OS: | Any |
| Assigned to: | Bogdan Degtyariov | CPU Architecture: | Any |
| Tags: | decimal, SQLColumns, TRANSFER OCTET LENGTH | ||
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
[28 Apr 2010 10:54]
Bogdan Degtyariov
[29 Apr 2010 8:34]
Bogdan Degtyariov
patch v2
Attachment: bug53235v2.diff (text/x-diff), 1.91 KiB.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.049 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.