Re: Re: DB_DataObjects save method

On Fri, 29 Oct 2004 17:33:54 -0400, Hans L <hans@velum.net> wrote: > >>Another option here (again, a Propel thing, sorry) is to just store the > >>columns that change. I'm trying to remember ... doesn't DBDO use the > >>overload methods __set() and __get() to store the db info? So I guess > >>in those methods you could store the modified columns (?). > > > > > > Only when you use it. It also allows direct setting/getting esp. for > > those of us on PHP4 where overloading either crashes PHP or breaks > > pass-by-ref. This simply would not work unless DO enforced this method > > of doing things. > > > > Ahh ... well, a good argument for why mutator methods are a good idea. > Alan & I have already disagreed on that :) > I agree that enforcing set/get would make things much cleaner and be more of a "real" OO concept. DO left behind the "simple container for data" idea *long* ago. -- paperCrane --Justin Patrin--