ERROR: invalid input syntax for integer: ""
Hi, ist there any known Bug in 3.0.10? 2011-10-31 15:26:16 CET [18344]: [327-1] user=otrs,db=otrsdb ERROR: invalid input syntax for integer: "" 2011-10-31 15:26:16 CET [18344]: [328-1] user=otrs,db=otrsdb STATEMENT: INSERT INTO queue_standard_response (queue_id, standard_response_id, create_time, create_by, change_time, change_by) VALUES ($1, $2, current_timestamp, $3, current_timestamp, $4) 2011-10-31 15:26:17 CET [18344]: [329-1] user=otrs,db=otrsdb LOG: duration: 89.126 ms execute <unnamed>: INSERT INTO queue_standard_response (queue_id, standard_response_id, create_time, create_by, change_time, change_by) VALUES ($1, $2, current_timestamp, $3, current_timestamp, $4) 2011-10-31 15:26:17 CET [18344]: [330-1] user=otrs,db=otrsdb DETAIL: parameters: $1 = '337', $2 = '179', $3 = '6', $4 = '6' Regards, Jens
Hi Jens, On Mon, 31 Oct 2011 16:00:03 +0100, Jens Wilke wrote:
ist there any known Bug in 3.0.10?
2011-10-31 15:26:16 CET [18344]: [327-1] user=otrs,db=otrsdb ERROR: invalid input syntax for integer: "" 2011-10-31 15:26:16 CET [18344]: [328-1] user=otrs,db=otrsdb STATEMENT: INSERT INTO queue_standard_response (queue_id, standard_response_id, create_time, create_by, change_time, change_by) VALUES ($1, $2, current_timestamp, $3, current_timestamp, $4)
No, it's now a known bug. When exactly did this happen? Were you creating a new queue? Are you using PostgreSQL as the database? -- Mike
On Wednesday 02 November 2011 09:47:22 you wrote: Hi Michiel,
No, it's now a known bug. When exactly did this happen? Were you creating a new queue? Are you using PostgreSQL as the database?
This happens on applying "Change Queue Relations for Response foo". It's the postgres error message that i sent. I found out, that there are 2 issues that might be responsible for this behavior. - The @IDs Elements are not uniq but 35 times repeated. - There's is an unecessary loop, that repetedly deletes and inserts the same values. Both are responsible for massive loops in AdminQueueResponses.pm The attached patch is a quick hack to fix these Problems. Regards, Jens
Hi Jens,
Thanks. I filed a bug report for it and corrected it in CVS. It will
be fixed in upcoming OTRS 3.0.12.
http://bugs.otrs.org/show_bug.cgi?id=7884
The bug report contains instructions for how to patch your OTRS 3.0.x
instance. The issue was that the 'select all' checkbox had an ID but
not a value, and OTRS tried to insert this as a standard_response (or
as a queue) when it was selected.
--
Mike
On Wed, Nov 2, 2011 at 11:18, Jens Wilke
On Wednesday 02 November 2011 09:47:22 you wrote:
Hi Michiel,
No, it's now a known bug. When exactly did this happen? Were you creating a new queue? Are you using PostgreSQL as the database?
This happens on applying "Change Queue Relations for Response foo". It's the postgres error message that i sent.
I found out, that there are 2 issues that might be responsible for this behavior. - The @IDs Elements are not uniq but 35 times repeated. - There's is an unecessary loop, that repetedly deletes and inserts the same values. Both are responsible for massive loops in AdminQueueResponses.pm The attached patch is a quick hack to fix these Problems.
Regards, Jens
_______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
On Saturday 05 November 2011 18:13:51 Michiel Beijen wrote: Hi Mike,
Why do you think that these loops are still required: 119 my %StandardResponseData 120 = $Self->{StandardResponseObject}->StandardResponseList( Valid => 1 ); 121 for my $StandardResponseID ( keys %StandardResponseData ) { 122 my $Active = 0; 123 for my $QueueID (@IDs) { 124 next if $QueueID ne $StandardResponseID; 125 $Active = 1; 126 last; 127 } 159 my %QueueData = $Self->{QueueObject}->QueueList( Valid => 1 ); 160 for my $QueueID ( keys %QueueData ) { 161 my $Active = 0; 162 for my $StandardResponseID (@IDs) { 163 next if $StandardResponseID ne $QueueID; 164 $Active = 1; 165 last; 166 } Regards, Jens
You're right. This was obsolete code and I've addressed this as well.
--
Mike
On Mon, Nov 7, 2011 at 09:41, Jens Wilke
On Saturday 05 November 2011 18:13:51 Michiel Beijen wrote:
Hi Mike,
Why do you think that these loops are still required:
119 my %StandardResponseData 120 = $Self->{StandardResponseObject}->StandardResponseList( Valid => 1 ); 121 for my $StandardResponseID ( keys %StandardResponseData ) { 122 my $Active = 0; 123 for my $QueueID (@IDs) { 124 next if $QueueID ne $StandardResponseID; 125 $Active = 1; 126 last; 127 }
159 my %QueueData = $Self->{QueueObject}->QueueList( Valid => 1 ); 160 for my $QueueID ( keys %QueueData ) { 161 my $Active = 0; 162 for my $StandardResponseID (@IDs) { 163 next if $StandardResponseID ne $QueueID; 164 $Active = 1; 165 last; 166 }
Regards, Jens _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
participants (3)
-
Jens Wilke -
Michiel Beijen -
Michiel Beijen