On Aug 5, 6:38 pm, Denver <[email protected]> wrote: > Alright, I appreciate the advise. > I will implement using clone(), and if performance seems to be high > afterward, I'll try to measure the difference and post about it. > > Thank you again! >
Yeah definitely load test this. clone() doesn't use a very sophisticated algorithm and can clone a very large object tree. lazy="true" helps a lot, but also adds load to the database since Transfer will requery as it loads each lazy object in the clone. In that same vein Matt's advice to always use clone() is incorrect. Quite often it's better to just update the actual object and save it unless you're changing relationships where the cache could become corrupt. clone() is one place where Transfer needs serious optimization (for instance not cloning parents until requested, and not walking back down child relationships on the parent). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
