Hello! RT 3.6.1
Could anyone predict the results of setting ticket's owner manually through simple SQL query: update Tickets set Owner = 123456 where id = 654321; ? I know that there are several tables updated in SetOwner method and I am interested what consequences such "brutal" workaround may cause. So far I've tested this query and it looks fine for ticket updating and resolving. If using this query multiple time eventually can trigger RT failure I wouldn't want to use it. Also, I would appreciate it very much if you could provide me with the list of tables updated during SetOwner. The reason I don't favor using SetOwner is that I do not know how to=) I'm trying to write a custom auto ticket assingment perl-module that should be put in crontab and I've just no idea how to utilize RT lib in there. Seriosly, I'm no programmer)) Any help and advice appreciated, Sincerely, Stan _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
