Ralf Eggert wrote: > > right now I am thinking about a problem with extendable models. To > explain this a bit, please think about a "jobs" table. This table has > some base columns like id, date, title, description and status. No > problem at all to build a model class with Zend_Db_Table and to build a > form with Zend_Form. > > Now, there are a couple of clients which need to extend this "jobs" > table with custom columns. For example client A wants to add a location > and a requirements column and client B wants to add the salary and a > services column. >
There's an article in this month's php|architect[1] entitled "EAV Modeling" that describes a way of handling situations very much like yours. Perhaps it could be of some use to you. [1] http://www.phparch.com/ -- View this message in context: http://www.nabble.com/Extendable-models-with-MySQL%2C-Zend_Db_Table-and-Zend_Form-tp18105740p18124652.html Sent from the Zend Framework mailing list archive at Nabble.com.
