There's been alot of talk reciently about the performance of propel within Symfony. To many users, tight Propel integration within the framework is one of the best features, so you can imagine some people's reaction when you tell them to rip it out and not use it.
As I'm trying to figure out ways around it I thought about using propel behaviors to interrupt any many of default behaviors and use sfFunctionCache to actually cache the results of propel function calls. In theory this would give you a light object model without the heavy work done by propel for each method call. Am I on the right track, or is just the inherit object structure too heavy regardless of the usage? Anyone have thoughts? Myke --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
