| Summary | Attachments limited to 64KiB |
| Queue | Horde Framework Packages |
| Queue Version | Git master |
| Type | Bug |
| State | Duplicate |
| Priority | 1. Low |
| Owners | Horde Developers (at) , chuck (at) horde (dot) org, jan (at) horde (dot) org |
| Requester | m.heimpold (at) web (dot) de |
| Created | 3/11/13 (4857 days ago) |
| Due | |
| Updated | 4/19/13 (4818 days ago) |
| Assigned | 3/11/13 (4857 days ago) |
| Resolved | 4/19/13 (4818 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
Bug 12195Assigned to Jan Schneider
Assigned to
State ⇒ Assigned
Queue ⇒ Horde Framework Packages
Version ⇒ Git master
Postgresql is ok as Horde_Db maps 'binary' to BYTEA, which is the
postgres LONGBLOB equivalent.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Attachments limited to 64KiB
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
the attachment is cut down to 64KiB. I'm using the VFS backend and
figured out that the attachments are store in mysql table 'horde_vfs'.
There is a field "vfs_data" of type BLOB. I simply "increased" this to
LONGBLOB and now attachments are working as expected.
(Using horde 5.0.4)