I'm a little on the fence about this. I obviously want to "catch up" and get up to 3.8.2 (whoohoo!) but I do need to sort out that ticket first (at least it would make sense...) to make sure it's not going to croak on the reload of the DB. I have looked at the nice relational drawing from the RT-Essential book, and from that I know better than just going into the DB like that and mess with the ticket... I can probably work it out, but I'd love to be able to get to keep that ticket (well, with the fixed bits in it). Would you share that SQL bits? At least, it'll give me a starting point...
Thanks, Jok > -----Original Message----- > From: Kenneth Crocker [mailto:[email protected]] > Sent: Thursday, February 26, 2009 11:22 AM > To: Joachim Thuau > Cc: [email protected] > Subject: Re: [rt-users] Ticket taken twice > > Joachim, > > > You could do this with SQL directly in the DataBase, > but I would only do that if Shredder can't handle it. I'm > afraid if you shred the ticket, it's gone and there won't be > a ticket to own. That might make your Audit department a > little testy about your ticket history. I have some SQL that > would help you, but you have to know it invloves more than > just the Ticket Table. There is the Group, Groupmember, ACL, > etc. tables. There is very little data in RT that does OT > relate to other tables. They ALL have to be insync. > > > Kenn > LBNL _______________________________________________ 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
