Hi Ralf, On Mon, Mar 18, 2013 at 2:25 PM, Ralf Hildebrandt < Ralf.Hildebrandt@charite.de> wrote:
otrs:/opt/otrs# cat scripts/DBUpdate-to-3.2.mysql.sql | mysql -p -f -u root otrs Enter password: ERROR 1091 (42000) at line 20: Can't DROP 'ticket_answered'; check that column/key exists
the ticket_answered column does exist in OTRS 3.1 databases (otherwise the ticket API would not work); so if it's not there when you run the DBUpdate SQL this is probably because this is the second time you ran it? Also re. your remark of the Full Text Index.
Also, the TABLE group_users had two full text indices which I had to remove due to the chamge from myisam -> innodb.
Full text indexes, really?? We never added those in OTRS code, many customers run on InnoDB and can't have those - or actually could not have those until MySQL 5.6. I think they might be added by your DBA... but they'll not be of much use unless you also implement the WHERE MATCH (fields) AGAINST (string) query somewhere in the OTRS code. -- Mike