db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "eCommerce Software Solutions Inc." <vinayso...@rogers.com>
Subject Re: Optimistic Locking
Date Wed, 21 May 2003 19:29:11 GMT
I deal with transactional systems only. Therefore, I am finding that JDO
(being very extensive in its coverage of such concepts and others) is the
long term solution. However, there is little option as far as free open
source JDO products are concerned. OJB is not easy to use and mature yet (I
am hoping that it will). Triactive JDO http://tjdo.sourceforge.net is an
evolving (and very compliant) open source product and I am experimenting
with it (looks good).

Hope this helps.



----- Original Message -----
From: "Keeney, Thomas" <KeeneyT@SEC.GOV>
To: "'Turbine Torque Users List'" <torque-user@db.apache.org>
Sent: Wednesday, May 21, 2003 7:55 AM
Subject: RE: Optimistic Locking


> That's an interesting proposal.  Do you have experience with OJB?  How
does
> it compare with Torque?  I'd like to migrate my apps from Torque to OJB,
but
> I'm under the impression that this is only necessary for highly
> transactional systems under heavy load.
>
> Regards,
>
> Tom
>
> -----Original Message-----
> From: eCommerce Software Solutions Inc. [mailto:vinaysoni1@rogers.com]
> Sent: Wednesday, May 21, 2003 12:10 AM
> To: Turbine Torque Users List
> Subject: Re: Optimistic Locking
>
>
> Such features involve more writing the same kind of code all the time. Why
> do that when it can be automated?
>
> A simple strategy could be: Torque run time makes an assumption that a
> uniquely named column serves as version id, can the torque run-time not
> check the version before performing the update. "Update" operation could
> take another parameter (Update.THROWOPTIMISTICEXCEPTION ) indicating that
> the optimistic policy is in use.
>
> However, with features like this Torque will become as feature rich as
JDO.
> I don't know if this is desirable and needed.
>
>
>
>
> ----- Original Message -----
> From: "Keeney, Thomas" <KeeneyT@SEC.GOV>
> To: "'Turbine Torque Users List'" <torque-user@db.apache.org>
> Sent: Tuesday, May 20, 2003 12:53 PM
> Subject: RE: Optimistic Locking
>
>
> > Please correct me if I'm wrong, but I don't believe Torque has this
> feature.
> > You could implement optimistic locking in your code by adding a
timestamp
> > that holds the last updated date for the Torque object.  Use the
timestamp
> > to rollback your transaction if the db record has changed since you
first
> > retrieved the Torque object.
> >
> > Does anyone else have other suggestions?
> >
> > Tom
> >
> > -----Original Message-----
> > From: eCommerce Software Solutions Inc. [mailto:vinaysoni1@rogers.com]
> > Sent: Friday, May 16, 2003 2:06 PM
> > To: Turbine Torque Users List
> > Subject: Optimistic Locking
> >
> >
> > Is this feature supported by torque ? I looked around but found no such
> > thing.
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-user-help@db.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-user-help@db.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>


Mime
View raw message