Can u pls mention what is that Oracle feature ?. Reading the data again is
time consuming.
- Original Message -
From: Johan Kok [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Sent: Monday, November 03, 2003 12:17 PM
Subject: RE: Design advice needed.
Anthony,
Did you
advice needed.
Can u pls mention what is that Oracle feature ?. Reading the
data again is
time consuming.
- Original Message -
From: Johan Kok [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Sent: Monday, November 03, 2003 12:17 PM
Subject: RE: Design advice needed
was did any DBA/DB development
work. Either go to the manual, or contact a oracle list.
-Original Message-
From: Antony Paul [mailto:[EMAIL PROTECTED]
Sent: 03 November 2003 09:10
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: Re: Design advice needed.
Can u pls mention what
the data again is
time consuming.
- Original Message -
From: Johan Kok [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Sent: Monday, November 03, 2003 12:17 PM
Subject: RE: Design advice needed.
Anthony,
Did you consider reading the record without locks, and when
: RE: Design advice needed.
Anthony,
Did you consider reading the record without locks, and when
an updated are
made, to take a write-lock, check that the original record
are still the
same and then apply, otherwise fail.
Your intentions might not work unless
- Original Message -
From: Jean-Louis [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, November 03, 2003 3:13 PM
Subject: Re: Design advice needed.
Hi,
you can use a timestamp and write for example :
update ...
where ...
and timestamp = 'the timestamp read by the select
This is what TopLink uses for optimistitic locking. Just don't forget to update the
timestamp in the update.
--Angus
-Original Message-
From: Jean-Louis [mailto:[EMAIL PROTECTED]
Sent: Monday, November 03, 2003 4:43 AM
To: Tomcat Users List
Subject: Re: Design advice needed
Anthony,
Did you consider reading the record without locks, and when an updated are
made, to take a write-lock, check that the original record are still the
same and then apply, otherwise fail.
Your intentions might not work unless all writes are passed through the
container, as Oracle will not
