Getting error:
" PG::StringDataRightTruncation: ERROR: value too long for type character varying(250) : UPDATE “tickets” SET “preferences” = $1, “note” = $2, “updatedbyid” = $3, “updated_at” = $4 WHERE “tickets”.“id” = $5"
Steps to reproduce the behavior:
Go to the ticket
Try to change the status
We’ve open customer ticket since 02/19 we cannot close.
" PG::StringDataRightTruncation: ERROR: value too long for type character varying(250) : UPDATE “tickets” SET “preferences” = $1, “note” = $2, “updatedbyid” = $3, “updated_at” = $4 WHERE “tickets”.“id” = $5"
Is the error msg, when we try to change the status of the ticket.
Sorry but without knowing more about your installation it’s impossible to help you.
I don’t know what kind of installation this is, but it doesn’t seem to be a vanilla Zammad installation?
By default the preferences field should be of length “text” which is by far more than 250 characters:
Table "public.tickets"
Column | Type | Modifiers | Storage | Stats target | Description
------------------------------+--------------------------------+------------------------------------------------------+----------+--------------+-------------
id | integer | not null default nextval('tickets_id_seq'::regclass) | plain | |
group_id | integer | not null | plain | |
priority_id | integer | not null | plain | |
state_id | integer | not null | plain | |
organization_id | integer | | plain | |
number | character varying(60) | not null | extended | |
title | character varying(250) | not null | extended | |
owner_id | integer | not null | plain | |
customer_id | integer | not null | plain | |
note | character varying(250) | | extended | |
first_response_at | timestamp(3) without time zone | | plain | |
first_response_escalation_at | timestamp(3) without time zone | | plain | |
first_response_in_min | integer | | plain | |
first_response_diff_in_min | integer | | plain | |
close_at | timestamp(3) without time zone | | plain | |
close_escalation_at | timestamp(3) without time zone | | plain | |
close_in_min | integer | | plain | |
close_diff_in_min | integer | | plain | |
update_escalation_at | timestamp(3) without time zone | | plain | |
update_in_min | integer | | plain | |
update_diff_in_min | integer | | plain | |
last_contact_at | timestamp(3) without time zone | | plain | |
last_contact_agent_at | timestamp(3) without time zone | | plain | |
last_contact_customer_at | timestamp(3) without time zone | | plain | |
create_article_type_id | integer | | plain | |
create_article_sender_id | integer | | plain | |
article_count | integer | | plain | |
escalation_at | timestamp(3) without time zone | | plain | |
pending_time | timestamp(3) without time zone | | plain | |
type | character varying(100) | | extended | |
time_unit | numeric(6,2) | | main | |
preferences | text | | extended | |
updated_by_id | integer | not null | plain | |
created_by_id | integer | not null | plain | |
created_at | timestamp without time zone | not null | plain | |
updated_at | timestamp(3) without time zone | not null | plain | |
last_owner_update_at | timestamp(3) without time zone | | plain | |
categoriy | character varying(255) | | extended | |
order_no | character varying(100) | | extended | |
order_info | character varying(50000) | | extended | |
title_internal | character varying(200) | | extended | |
production_site | character varying(50000) | | extended | |
This should be similar to a MySQL installation as well.
Even without migrations this should be already perfectly fine as our default ticket-table creatrion sets the limit to 500kb:
Again, as I know nothing about your installation (you removed the important information from the template) I can’t help further. Or at least not in a usefull way.
It however doesn’t seem to be related to the issue you’ve been posting on earlier this week.
Edit: Oh and technically it doesn’t have to do anything with the state but should affect anything on this ticket - so even updating the owner.