[Chris..] > I use CakePHP for a project at work and all those queries only happen > when you're in debugging mode and it's not caching anything. In > production mode, it will cache all those queries that tell it what the > database structure is.
Ah OK, that's better then! > It's important to realize that any sort of DB wrapper comes with > overhead. Indeed. As does the existence of a framework in the first place - but it saves developer time and makes things easier to maintain which is the whole point. [Markus..] > Personally, I prefer the "convention-over-configuration" style anyway > these days. I totally agree, and believe convention should be used wherever possible in ZF to make life easier (ie. default view template names, etc). > It becomes more difficult when trying to use a legacy schema > where you have no influence in the naming of your table columns. In Rails, for example, you can specify table and field names to get over this. As long as ZF has this kind of flexibility all will be fine. Si
