If you baked your application then each controller already has the delete function in it. I would add functionality in there that delete doesn't delete it just updates active field. Also, keep in mind that you don't have to deactivate every single record. If for instance comments belong to a post. If you deactivate (delete) the post you don't have to deactivate all the comments. Since during the normal course of your application you never really get at comments other than thru the post. So, if the post never shows anywhere, then the comments won't either.
So, in this manner you would only need to worry about your container models and deactivating them. Of course, you could also get really complex I guess and make a whole new application that ties to another database. Make like a history controller and have it use a seperate database. The history controller would just take records and save them there. Without knowing exactly what your application does, and its parameters I can't help much past this. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
