Redmine

The details of the tables:

mysql> describe journal_details;
+------------+-------------+------+-----+---------+----------------+
| Field      | Type        | Null | Key | Default | Extra          |
+------------+-------------+------+-----+---------+----------------+
| id         | int(11)     | NO   | PRI | NULL    | auto_increment |
| journal_id | int(11)     | NO   | MUL | 0       |                |
| property   | varchar(30) | NO   |     |         |                |
| prop_key   | varchar(30) | NO   |     |         |                |
| old_value  | tinytext    | YES  |     | NULL    |                |
| value      | tinytext    | YES  |     | NULL    |                |
+------------+-------------+------+-----+---------+----------------+
6 rows in set (0.00 sec)

mysql> describe issues;
+------------------+--------------+------+-----+---------+----------------+
| Field            | Type         | Null | Key | Default | Extra          |
+------------------+--------------+------+-----+---------+----------------+
| id               | int(11)      | NO   | PRI | NULL    | auto_increment |
| tracker_id       | int(11)      | NO   | MUL | NULL    |                |
| project_id       | int(11)      | NO   | MUL | NULL    |                |
| subject          | varchar(255) | NO   |     |         |                |
| description      | text         | YES  |     | NULL    |                |
| due_date         | date         | YES  |     | NULL    |                |
| category_id      | int(11)      | YES  | MUL | NULL    |                |
| status_id        | int(11)      | NO   | MUL | NULL    |                |
| assigned_to_id   | int(11)      | YES  | MUL | NULL    |                |
| priority_id      | int(11)      | NO   | MUL | NULL    |                |
| fixed_version_id | int(11)      | YES  | MUL | NULL    |                |
| author_id        | int(11)      | NO   | MUL | NULL    |                |
| lock_version     | int(11)      | NO   |     | 0       |                |
| created_on       | datetime     | YES  | MUL | NULL    |                |
| updated_on       | datetime     | YES  |     | NULL    |                |
| start_date       | date         | YES  |     | NULL    |                |
| done_ratio       | int(11)      | NO   |     | 0       |                |
| estimated_hours  | float        | YES  |     | NULL    |                |
| parent_id        | int(11)      | YES  |     | NULL    |                |
| root_id          | int(11)      | YES  | MUL | NULL    |                |
| lft              | int(11)      | YES  |     | NULL    |                |
| rgt              | int(11)      | YES  |     | NULL    |                |
| is_private       | tinyint(1)   | NO   |     | 0       |                |
| closed_on        | datetime     | YES  |     | NULL    |                |
+------------------+--------------+------+-----+---------+----------------+
24 rows in set (0.00 sec)

I think that the problem is the "tinytext" type in the case of old_value and the "text" type in case of description. Because if a modify a big text of description, there is no space in old_value??

The only plugin I use is DMSF.

if you need more feedback, ask me. Thanks,

I think it is bug of rails or mysql adapter in old version.
#20831, #21993, #21123#note-6.
Try #20831#note-3.

I think this bug is more related to #21993 than to #20831#note-3. #21993 discovers problems between text fields of the database with different size limits and #20831#note-3 is related to a migration problem between SQLite and MySQL. In this case, I think the problem is different size of text fields of the database (like #21993).

The db/schema.rb for issues table is:

  create_table "issues", force: :cascade do |t|
    t.integer  "tracker_id",       limit: 4,                     null: false
    t.integer  "project_id",       limit: 4,                     null: false
    t.string   "subject",          limit: 255,   default: "",    null: false
    t.text     "description",      limit: 65535
    t.date     "due_date" 
    t.integer  "category_id",      limit: 4
    t.integer  "status_id",        limit: 4,                     null: false
    t.integer  "assigned_to_id",   limit: 4
    t.integer  "priority_id",      limit: 4,                     null: false
    t.integer  "fixed_version_id", limit: 4
    t.integer  "author_id",        limit: 4,                     null: false
    t.integer  "lock_version",     limit: 4,     default: 0,     null: false
    t.datetime "created_on" 
    t.datetime "updated_on" 
    t.date     "start_date" 
    t.integer  "done_ratio",       limit: 4,     default: 0,     null: false
    t.float    "estimated_hours",  limit: 24
    t.integer  "parent_id",        limit: 4
    t.integer  "root_id",          limit: 4
    t.integer  "lft",              limit: 4
    t.integer  "rgt",              limit: 4
    t.boolean  "is_private",                     default: false, null: false
    t.datetime "closed_on" 

So, the description filed is limited to 65535. However, the old_value of journal_details table in db/schema.rb is limited to 255:

create_table "journal_details", force: :cascade do |t|
    t.integer "journal_id", limit: 4,   default: 0,  null: false
    t.string  "property",   limit: 30,  default: "", null: false
    t.string  "prop_key",   limit: 30,  default: "", null: false
    t.text    "old_value",  limit: 255
    t.text    "value",      limit: 255

(I cannot provide a patch because I am not a ruby/rails developer)