Defect #47

Error in journalizing an issue with longtext custom fields

Added by Amedeo Amedeo 492 days ago. Updated 492 days ago.

Status:Closed Start:
Priority:Normal Due date:
Assigned to:- % Done:

0%

Category:-
Target version:-

Description

When an issue has custom fields defined as longtext, whenever you try to save a very long text description (more than
255 chars) the system fails saving on table journal. This is due to the size of 255 for oldValue and newValue fields.

I managed temporarily with the attached patch.

issue.patch (1.6 KB) Amedeo Amedeo, 2008-02-03 10:49

History

2007-04-24 11:26 - Jean-Philippe Lang

I see 2 solutions:
- change the 2 database columns to 'text' (instead
of varchar255)
- truncate the values (as you did in your patch)

Do you need to have the full length value in the history ?

2007-04-24 11:31 - Amedeo Amedeo

I would go for the truncation, don't think has a real value having
a very long
decription in the history and also depending on the database
implementation
having text field rather than varchar(255) could increase
drammatically the size
of the journal table.

Thanks,
Amedeo

2007-04-24 11:34 - Jean-Philippe Lang

I agree with you. I'll fix this way.
Thanks.

2007-04-24 11:41 - Jean-Philippe Lang

I've just tested this. I get no errors and text is automaticaly
truncated and correctly saved.

Could tell me what version of rails and database you're using ?

2007-04-24 12:04 - Amedeo Amedeo

Rails 1.2.2 and PostgreSQL 8.1.4

The error I get is something like:

RuntimeError: ERROR C22001 Mvalue too long for type character
varying(255) Fvarchar.c L539 Rvarchar: INSERT INTO journal_details
("old_value", "property", "value",
"journal_id", "prop_key") VALUES('', 'cf',
'Lorem ipsum dolor sit amet

2007-04-24 12:20 - Jean-Philippe Lang

This problem doesn't occur with mysql. But I could reproduce
it after swithing to Postgresql.

Fixed in rev 477.

2007-04-24 12:25 - Amedeo Amedeo

Thanks for the prompt action :)

Also available in: Atom PDF