On 10/25/06, Simon R Jones <[EMAIL PROTECTED]> wrote:
To answer your first question Nick, we are using Zend_Db_Table on two live
e-commerce sites successfully, though only for the admin side of things.
We have used Cake framework in the past and have been rather shocked at the
number of SQL requests it makes to understand a table structure. So I'm
certainly unhappy about doing that on a front-end site. So Markus's thought
of using a mapping file of some kind to describe the data makes a lot of
sense.
Hey Simon,
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. I think any sort of Active Record / ORM
implementation either has to cache the table structures (allowing you
to alter tables on the fly and have the new fields show up after an
webserver restart) or you mess around with configuration files to make
those changes available to your application. Since I'm a lazy
programmer, I prefer the convention-over-configuration path and like
implementations that cache the table structure information.
It's important to realize that any sort of DB wrapper comes with
overhead. Anyone else who tells you otherwise is either misinformed
or lying. Besides, any sort of large-scale application ends up having
a custom DB wrapper. I can't imagine ActiveRecord scaling very well,
but I may be wrong.
--
Chris Hartjes
"The greatest inefficiencies come from solving problems you will never have."
-- Rasmus Lerdorf
@TheBallpark - http://www.littlehart.net/attheballpark
@TheKeyboard - http://www.littlehart.net/atthekeyboard
