> On 2000.12.06 02:07:26 +0000 John McNally wrote:
> > Oops. Something like what you suggest will probably be necessary.
> > Still considering using an inner class, also. I am adding quite a few
> > methods in addition to the save(). I will try to get something in for
> > you to look at within the next couple days. The addSaveMethod property
> > in torque.props should probably be set to false for now. Will do.
>
> <fx="petualant child">but I WANT a save method!</fx>
>
> Seriously, that's cool - I'll check out what you do and sort myself out a
> quick kludge so that I can use the save method for the moment.
>
> --
> Sean Legassick
I believe all the problems with save method (which I also love) root from
the fact that "newness" of a record is determined by it's autogenerated ID
being unset which seems to be a bad idea, because tables may not have such
an ID at all (x-ref tables for example). So I think the right way to to it
is to add a boolean property isNew to BaseObject which would be true by
default and would be set to false either in it's save() method or when it's
loaded by it's Peer.
John, could you implement this while you are there? Or I can do that - come
over to IRC to coordinate this.
fedor.
_______________________________________________________
Tired of slow Internet? Get @Home Broadband Internet
http://www.home.com/xinbox/signup.html
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
