Hi, the first case is easy. Use an editor to search for all files containing Peer::
The second case we also did manually (and actually today I discovered propel bug in one join method for 1.3). I think they are easy to spot. Usually you have some larger sql statements, selecting from more than one tables. If there are plenty (ideally linear to the amount of data you see on the page) then you most likely have spotted something for case 2. Then you need to check the part that queries the data and add the join. Unfortunately I do not see any good automatic way to optimize this. But once you have figured out the "mechanics" of a certain issue, you can again do a search in all files. Another example, where I on Saturday gained some performance, can be found on my blog: http://www.hma-info.de/blog/2007/12/25/reduce-unneeded-propel-sql-queries-as king-for-an-id/ .: Fabian -----Original Message----- From: [EMAIL PROTECTED] om [mailto:[EMAIL PROTECTED] groups.com] On Behalf Of Ian P. Christian Sent: Dienstag, 25. Dezember 2007 15:37 To: [email protected] Subject: [symfony-users] identifying queries generated in the view Hi all, I'm wondering if anyone's come up with a method to identify queries generated inside template logic? I'm reviewing a site already written in symfony/propel, and there's quite a few places where queries are done in templates - either directly by calls to Peer methods, or indirectly, via accessing un-joined objects (like $obj->getSomething()->getName() generating a query to load 'something'). Any ideas? Thanks, Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
