Consider increasing the size limit of description and note columns for tickets
Currently for MySQL (haven't tested other databases) the
journal.notes fields are of type
text. I attempted to post a detailed report of some work I was doing earlier to a Redmine installation I run and encountered the cap for the
text type. I had opted to post the details directly into the OP instead of a text file attachment because I was hoping to have the contents of the report searchable.
Notepad++ tells me the length of the content is 69161, which I assume is characters. I spent a while researching (since I am not a MySQL expert by any means) and came upon these references:
According to the last link the
text type is:
A TEXT column with a maximum length of 65,535 (216 − 1) characters. The effective maximum length is less if the value contains multibyte characters. Each TEXT value is stored using a 2-byte length prefix that indicates the number of bytes in the value.
If I understand the details correctly (I'm still new), these field types are of variable length, so if the type were changed to
MEDIUMTEXT the cap would be raised from 65,535 bytes to 16,777,215 bytes but the actual storage required for only a small amount of content would be based on the amount of actual content.
Please consider adjusting the field types for these and related columns in a future Redmine release in order to support larger descriptions and comments on issues.
Thank you for your consideration.
#3 Updated by okkez _ over 5 years ago
- File 0001-Raises-journals-notes-limit-to-4GB-19869.patch added
- File 0002-Raises-issues-description-limit-to-4GB-19869.patch added
I've created patches for this issue.
In my case, I want to change DB from SQLite3 to MySQL.
SQLite3's text type can contain unlimited size of text.
But MySQL's text type is limitted to 64KB.
So I have to change these column's limit.