You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Eric Dobbs <er...@dobbse.net> on 2001/10/31 18:16:32 UTC
Re: transaction management (RE: cvs commit: jakarta-turbine-torque NO TES)
On Wednesday, October 31, 2001, at 08:44 AM, Jason van Zyl wrote:
> On 10/31/01 10:19 AM, "Fedor Karpelevitch"
> <fe...@Barra.COM>
> 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()
-Eric
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: transaction management (RE: cvs commit:jakarta-turbine-torque NO TES)
Posted by Fedor Karpelevitch <fe...@home.com>.
i guess there should be setDeleted() and save()
On 31 October 2001 11:56, you wrote:
> 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" <er...@dobbse.net> wrote:
> > > On Wednesday, October 31, 2001, at 08:44 AM, Jason van Zyl wrote:
> > >> On 10/31/01 10:19 AM, "Fedor Karpelevitch"
> > >> <fe...@Barra.COM>
> > >>
> > >> 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:
> > > <ma...@jakarta.apache.org> For additional
> > > commands, e-mail: <ma...@jakarta.apache.org>
> >
> > --
> >
> > 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:
> > <ma...@jakarta.apache.org> For additional
> > commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: transaction management (RE: cvs commit:jakarta-turbine-torque NO
TES)
Posted by John McNally <jm...@collab.net>.
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" <er...@dobbse.net> wrote:
>
> >
> > On Wednesday, October 31, 2001, at 08:44 AM, Jason van Zyl wrote:
> >
> >> On 10/31/01 10:19 AM, "Fedor Karpelevitch"
> >> <fe...@Barra.COM>
> >> 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: <ma...@jakarta.apache.org>
> > For additional commands, e-mail: <ma...@jakarta.apache.org>
>
> --
>
> 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: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: transaction management (RE: cvs commit:
jakarta-turbine-torque NO TES)
Posted by Jason van Zyl <jv...@zenplex.com>.
On 10/31/01 12:16 PM, "Eric Dobbs" <er...@dobbse.net> wrote:
>
> On Wednesday, October 31, 2001, at 08:44 AM, Jason van Zyl wrote:
>
>> On 10/31/01 10:19 AM, "Fedor Karpelevitch"
>> <fe...@Barra.COM>
>> 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: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>