Hi, Andrew wrote: > So 1.8.4 should resolve this?
Yes, it's in the current version. > On a tangential note, this is a common issue I seem to have with ZF > database handling. There is a lot I like about the framework, but it > does not seem to lend itself to a design paradigm that uses stored > procedures for database access. True, you CAN execute procedures via > the framework, but all of these built-in goodies are dependent on > Zend_Db_Table and lean heavily toward granting full access to all > objects in the database. It would be nice to see some of the features > like Db_RecordExists accept arrays and/or Zend_Config instances where > you could optionally define a procedure name and some parameters > rather than just a table and column name. The framework should work on most environments. Not every Database-Engine supports stored procedures. Currently you can just change the used DBE in your configuration file and your application is still working. If you have specific requirements to meet, you can just easily extend any ZF class. For example, we overwrote the query method in the validator, because we don't wanted that every column got fetched. It wasn't a problem. Now, after that got fixed in the current release, we just needed to change the class names... -- Regards, Thomas
