Join GitHub today
Why is the Soft Delete behavior deprecated? #810
The Soft Delete behavior (http://propelorm.org/Propel/behaviors/soft-delete) is marked as deprecated "due to limitations that can't be fixed". What are those limitations? I tried to search this repository for information on soft delete, but could not find the smoking gun.
The Soft Delete behavior is almost exactly the functionality that I am looking for, whereas Archivable is the exact opposite of what I want (actually used a system with 3-4 levels of archive tables years ago. It was just a headache making sure data wasn't lost. It was).
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
As far as I know, it's just "deprecated" in sense of it's not actually maintained or developed any further. I'm also convinced,
I'm still using both behaviors for different objectives, feel free to use both.
I was also wondering basically the same thing: Why is Soft Delete not available for Propel 2? A google search lead to http://stackoverflow.com/questions/2519297/does-propel-know-when-an-object-has-been-soft-deleted-so-that-child-entities-co which lead to http://propelorm.org/blog/2011/08/29/introducing-archivable-behavior-and-why-soft-delete-is-deprecated.html