Hi Allessandro,
thanks for your kind reply.
I did some research as well, and created a slightly different fix that will
also make it possible to add new queues:
[pete@otrs1 postgres]$ diff /opt/otrs/Kernel/System/Queue.pm
/opt/otrs/Custom/Kernel/System/Queue.pm
671a672,677
> foreach my $key (qw(UnlockTimeout FirstResponseTime FirstResponseNotify
> UpdateTime UpdateNotify SolutionTime SolutionNotify)
> ) {
> $Param{$key} eq '' and $Param{$key} = undef;
> }
> $Param{'FollowUpLock'} eq '' and $Param{'FollowUpLock'} = 0;
>
Though I have to agree that your solution is more elegant.
However, I am a bit concerned that the same misconception (essentially the -
wrong, by ANSI standard - assumption that an empty string will be accepted as a
NULL value by the database) might also show up at other, not so obvious, places
in the code. I'll watch the database logs, just in case.
Thanks and best regards,
Peter.
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
