delete() could entail deleting the information from the db, possibly preceded by copying the data into an archive, or it could mean save() preceded by setting a DELETED flag to true. Does delete() only cover the first part of the first way of deleting?
john mcnally Jason van Zyl wrote: > > On 10/31/01 12:16 PM, "Eric Dobbs" <[EMAIL PROTECTED]> wrote: > > > > > On Wednesday, October 31, 2001, at 08:44 AM, Jason van Zyl wrote: > > > >> On 10/31/01 10:19 AM, "Fedor Karpelevitch" > >> <[EMAIL PROTECTED]> > >> wrote: > >> > >>> I understand Jason's point. However I believe we still need > >>> save(DBConnection) (or replacement) type of methods. > >> > >> Sure, it's required now because we haven't implemented a replacement or > >> redesigned it but the interface an OM object adheres to should be as > >> simple > >> as possible. Do we really need more than save()/update()/delete()? > > > > or even just save() and delete() > > yes! > > > -Eric > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- > > jvz. > > Jason van Zyl > > http://tambora.zenplex.org > http://jakarta.apache.org/turbine > http://jakarta.apache.org/velocity > http://jakarta.apache.org/alexandria > http://jakarta.apache.org/commons > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
