Hi Jon I am just about to implement this exact functionality in an application. Like you, I also think that it would be a logical piece of functionality to include in the Cake core. After all, soft delete has exactly the same set of issues attached to it (cascading for instance) as does regular delete.
Mariano says that it is so simple to implement that you wouldn't put it in the CakePHP core. Why then put delete in the core? Surely it would be just as simple to implement? What attracts me to Cake is that stuff like deleting is simple to do. As a "consumer of Cake" (as opposed to a developer), I would find soft deletes a useful feature to have built in. Obviously this is just my personal opinion / 2 cents worth etc :-) I would be interested to hear the reasons for not including this sort of functionality. Is is a matter of bloat? Regards, Langdon Jon Bennett wrote: > ... to add to core? > > I've just reworked some core cake code (very slightly!), so I could > have a cascadable, softDelete function, and have realised that if cake > followed 1 more convention, it could be very easy to add this into the > core. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
