On Fri, Jan 22, 2010 at 7:51 PM, Meroe Meroe <[email protected]> wrote:
> What about using some sort of service method? That way you separate some of > the logic in the service and tie that to the model only if needed? Just a > thought. > > Honestly? Because I don't really understand very much about what we mean by "service" and "service layer." If we mean, esssentially, abstracting away the dirty details of data persistence, I don't think that's really necessary for the app I'm working on. I am prepared to be married forever to a RDBMS backend -- indeed, to MySQL. (MySQL: with this ring I do thee wed.) > > On Fri, Jan 22, 2010 at 4:00 PM, David Mintz <[email protected]> wrote: > >> I have a situation in which certain controller actions need to use an >> instance of my Model_DbTable_Foo (which extends Zend_Db_Table_Abstract), but >> those actions also instantiate my Zend_Form subclasses, which also need >> access to Model_DbTable_Foo for getting data to populate select menu >> options.[....] >> >> > -- Support real health care reform: http://phimg.org/ -- David Mintz http://davidmintz.org/
