On the other hand, it wouldn't take a lot of code or any significant overhead to run a few queries to see what the user has in the database. Further, I believe that in a data-destroying operation like this, there should be a warning message by default and a --force option if you really don't want to hear about it ;-)
Aaron On Tue, 17 Jun 2003, Matthew T. O'Connor wrote: > > If i delete a user is aliases are not deleted thats not a big problem i > > just delete via a script is aliases (dbmail-aduser c user -a aliases) > > before i delete that user. > > > > But what about is old mailboxes and messages in the > > mailboxes, messages, messageblks tables. > > I would think this is best handled via referential integrity from the > database. I added all the foreign key relationships that seem relevant to > my postgres setup, this guarantees that everthing associated with the > user gets deleted when the user is deleted (or won't let you delete the > user while there is data dependentand on the user, depending on how the > foreign key was setup). > > > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail >
