Jeff Watkins wrote: > On 15 Nov, 2005, at 7:54 am, [EMAIL PROTECTED] wrote: > > the .set() method ? > > The real problem with the set method is it forces me to collect all > my changes in some other place before I can apply them to the model > object. This means my model object doesn't reflect the current state > and is worthless when passing to another method.
agree, I have mentioned that in another other post a few days ago :-( One work around I am using(pretty dumb) is to create a "internal dict" in the SQLObject class and updates there. Of course, it becomes a "coding policy" issue of which value should be used(from the object itself, or the internal dict).
