ok, so it seems that you are not convinced of relocating the save methods,
and so the default location of the save methods should stay as they are.
I'd then go for the following:
- modify the template for the save methods such that it can be used in the
peer classes as well as in the dbobject classes (from looking at it this
should not bee too difficult)
- add a generation option for the location of the save methods, defaulting
to the dbobject methods.
ok ?
If the location of the save methods is the peer classes, public isSaving()
and setSaving() methods are needed. Is it ok to add them even if the save
methods are in the dbObject methods (in the spirit of TORQUE-116 )
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
