On 11/27/07, rihad <[EMAIL PROTECTED]> wrote: > - while listing db records you usually don't need all the columns, but > only some of them. Propel fetches them all. The lazyLoad "feature" > quickly becomes anti-optimization if you dare access more fields > later, each new access resulting in a separate db hit. Same thing goes > for a detailed view of the said items by clicking on its link. I had > to work around all this by using SQL views listing only needed > columns, and building the models on them.
Out of curiosity, how does Doctrine solve this problem? -- - SR --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
