I had the memory problem too during a huge database query, where propel creates thousands of objects in a little overkill way :) So, i went one abstraction level down and did normal querys with creole. Look at http://www.symfony-project.com/askeet/14 to see how this is down (method getTagsForUserLike).
You can pimp your performance extremly, when you go this way for big querys. - Frank Am 22.03.2007 um 12:18 schrieb ved: > > Thanks all for your reply, > > The problem what I have figured out is with propel jointable. There > are already tickets open on propel site for the same. Only when you > have a large table with reference(s) to table(s) that causes this > problem. > > I cannot quit the batch in between, and moreover thats not a solution. > I would still consider using native mysql code and updating/inserting > the required data. Its light and never gave me problem. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en -~----------~----~----~----~------~----~------~--~---
