
Robert, here are some ideas on the deleting user requirement. I added a DeleteUser in User.pm and a GetUserTickets in Ticket.pm. I'm not sure if they work as written as I have yet to get all of otrs installed on my systems, but, they should be close. On Thu, 2004-01-08 at 02:47, Robert Kehl wrote:
On Friday, December 26, 2003 3:34 AM Mark Mertel
wrote: It would probably be a good idea for the long term to provide a delete method in the object model for each object which can be saved to the database. Within these methods could be handled any type of action regarding cascading deletes, or updating any reference tables with some default value, i.e. if you wished to delete a user you would probably want to update any trouble tickets created by that user toi some system user account.
A feature like the above is most likely to be built in the near future. Feel free to contribute ideas and/or concrete patches/code on the developers' list dev@otrs.org.
Robert Kehl
-- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Tel. +49 (0)6172 4832388
_______________________________________________ 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 Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/ -- Mark Mertel mmertel@olympus.net Mobile 206.409.2018 Phone 206.322.9074