Hi John, thanks. Yeah the way I see its implementation working would be to keep the delete method invoketion the same, just change its implementation dependant on the XML configuration, this would allow some objects to be properly deleted and other only soft deleted likewise with cascading the deletes, sometimes I'll want a parent object to be soft deleted but its children are not audited so they can be properly removed :-)
I kind of remember someone mentioning it was on the roadmap when I last asked a few months back, perhaps I'll play around with some patches and suggestions for Mark and see if I cant accelerate it a little. Rob On Mar 3, 4:01 pm, John Whish <[email protected]> wrote: > I believe that soft delete is already on the road map. I haven't tried it, > but you should be able to overwrite the Transfer save method to do an update > instead of a delete. So you code would still call the delete method. --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
