The description for max_attachment_size should mention max_allowed_packet, either unconditionally, or if possible only if MySQL is in use. Otherwise, an admin could raise max_attachment_size but it wouldn't work and they'd be surprised as to why. Gerv
The documentation already mentions this, and if you set max_attachment_size > max_allowed_packet, Bugzilla already throws an error explaining that you must first increase max_allowed_packet. No need to make the description more verbose. IMO, a param description is not the right place to explain how to configure your DB server.
Severity: normal → trivial
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
(In reply to Frédéric Buclin from comment #1) > The documentation already mentions this, and if you set max_attachment_size > > max_allowed_packet, Bugzilla already throws an error explaining that you > must first increase max_allowed_packet. Well actually, it says (in check_maxattachmentsize in Common.pm): return "You asked for a maxattachmentsize of $byte_size bytes," . " but the max_allowed_packet setting in MySQL currently" . " only allows packets up to $max_packet bytes"; Which is not all that informative. It doesn't tell you how to change it, or where. Moving to Documentation - when the new docs are done, we can add a link here to explain. Gerv
Assignee: administration → documentation
Status: RESOLVED → REOPENED
Component: Administration → Documentation
Resolution: WORKSFORME → ---
You need to log in before you can comment on or make changes to this bug.