Dear RT-users,
is there a documentation for the RT database structure somewhere?
Specially I need to know (but don’t understand), where and how the
Requestor, Cc and AdminCc of a specific request are stored in the DB
(MySQL), so that we can change them with MySQL batch jobs.
RT1 was a little bit more straightforward in this respect 
Thanks in advance
frank
Frank Thommen, Informatik Support Gruppe, D-INFK, ETH Zuerich
E-Mail: fthommen@inf.ethz.ch; Tel: +41-1-63 27208 (Mo-Do)
Web: http://www.isg.inf.ethz.ch
At 01:28 PM 12/19/2003, Frank Thommen wrote:
is there a documentation for the RT database structure somewhere?
I believe there was documentation for RT2’s database out there, which is
similar, but obviously not the same.
RT1 was a little bit more straightforward in this respect
Which is exactly the reason why you shouldn’t go mucking in the database
directly. It is strongly encouraged that you use the API for accessing the
RT database. It takes care of all the complications for you.
Michael
Michael S. Liebman m-liebman@northwestern.edu
http://msl521.freeshell.org/
“I have vision and the rest of the world wears bifocals.”
-Paul Newman in “Butch Cassidy & the Sundance Kid”
RT1 was a little bit more straightforward in this respect
Which is exactly the reason why you shouldn’t go mucking in the database
directly. It is strongly encouraged that you use the API for accessing the
RT database. It takes care of all the complications for you.
Hmm. I’d love to, but there are 116 (!) libraries, through with we’d
have to scroll and I didn’t find any overview/outlay/synopsis of the
overall structure of the libraries. Most of the libraries’
documentation is quite marginal (only raw function descriptions, no
examples, no overviews).
frank