Project

General

Profile

Actions
Copy link

Defect #20831

closed

journal_details table reverted value and old_value back to String on update from 2.6.0 to 3.1.1

Added by John Janus about 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Database
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:
3.1.1

Description

I recently upgraded our redmine installation from 2.6.0 to 3.1.1.
Since then it has not been possible to edit descriptions.
The log shows the following error:

Mysql2::Error: Data too long for column 'value' at row 1: INSERT INTO `journal_details` (`property`, `prop_key`, `old_value`, `value`, `journal_id`) VALUES ('attr', 'description', '<long description here>',2068)
The same error message appears for old_value.

I found Defect #15483, which describes a similar problem.
A quick check in the database shows, that the type for old_value and value is indeed varchar(255).
BUT in the database for the 2.6.0 version, those columns had varchar(255) as type as well, though editing a description was possible there.

Version 2.6.0 was installed without prior data on a windows server with the bitnami stack (mysql as database).
3.1.1 was installed on a linux server with mariadb 10.0.20. the database was dumped from the windows mysql server and read into the mariadb without problems.

Files

Download all files
sqlite3-to-mysql.py (1.08 KB) sqlite3-to-mysql.py translate a sqlite3 dump into MySQL format. Anonymous, 2016-01-04 10:23
dump_error.log (13.1 KB) dump_error.log Full error stack Anonymous, 2016-01-04 10:55

Related issues

Related to Redmine - Defect #15483: Error 500 on Issue Update (postgres)Closed

Actions
Has duplicate Redmine - Defect #23741: unable to modify the issue descriptionClosed

Actions
Actions
Copy link

Also available in: Atom PDF