Hi Henning, yes, you are right. This would be the easiest way. But I'm not very happy with this, because every year 10,000 students are leaving our university and all would produce empty entries.
I'm not very familiar with databases. Will we run into performance problems, if there are so many new entries every year? Greetings Martin > -----Ursprüngliche Nachricht----- > Von: dev-boun...@otrs.org [mailto:dev-boun...@otrs.org] Im Auftrag von > Henning Heil > Gesendet: Freitag, 22. Februar 2013 10:25 > An: Development community of OTRS > Betreff: Re: [dev] How to Delete Customer? > > Hi all, > > David Boyes schrieb am 21.02.2013 16:45: > > > > As of now we only have an option to make customer invalid by setting > Valid=0. > > > > Do we have any option to permanently delete the customer? > > David is right, there is no need and no good reason to risk the integrity of > the > database by simply deleting the records. > > If you need to comply with a data privacy act, why not simply blank the fields > with personal data but leave the record itself in place? > > Have you tried something like > > UPDATE `customer_user` SET `last_name`=`` WHERE `valid`=0; > > ? (SQL untested; you have to add the other fields) (please do a backup > before playing with the database) > > If you blank or NULL the respective fields there would be no personal data > left and legal aspects would be o.k. > > Greets, > > Henning > > > > > _______________________________________________ > OTRS mailing list: dev - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/dev > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
