Hi, I have a medium complex application. Some objects have several dependencies (foreign keys).
In a fancy OO application I should get several populated beans and set in the main object. The problem I see is in some cases I just want to save the main object, and in such cases I just need the foreign keys from the dependent objects. I worry if it could lead to some performance problems in a high accessed site or if it's worth to just setForeignKey() in that cases. What do you think about that? Is there any situation where you have a setClient( client ) and a setClientID( clientID )? So I can just setClientID() and my clientService.save() use the client.getClientID(). This would avoid loading some many unneeded objects. The problem I refer is when I have an object (i.e. order) with some many dependencies (client, product, category and so on.) There are some dependent objects having a huge bunch of set()s. Thank you, Ronan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" 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/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
