Hi
I more or less successfully update our OTRS installation from 2.2.8 to
3.0.11 and almost everything seems to work and we all love the new look
and feel.
However, when creating a new queue, we get an SQL error:
ERROR: null value in column "move_notify" violates not-null constraint,
SQL: 'INSERT INTO queue (name, group_id, unlock_timeout,
system_address_id, calendar_name, default_sign_key, salutation_id,
signature_id, first_response_time, first_response_notify, update_time,
update_notify, solution_time, solution_notify, follow_up_id,
follow_up_lock, valid_id, comments, create_time, create_by, change_time,
change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
current_timestamp, ?, current_timestamp, ?)'
I chcked on the (PostgreSQL) database, table queue has a column
move_notify with a not-null constraint, and the SQL statement being used
by OTRS does _not_ set that column in the insert statement above.
So the DB is right to yell at us here.
Is that rather a bug in the code or should the column "move_notify" have
been dropped during the upgrade?
Thanks for any hints,
Marc Balmer, micro system
---------------------------------------------------------------------
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
