Hello Carlos,
To add to the original query :
Taking the case of the highest isolation level
(Serialisable) i presume that the table would be locked when one instance
has selected a row but has not commited any changes. The other instance
would not be able to even select the data from that row unless the first
instance puts in the commited changes.
Will this not affect the performance terribly (ofcourse, at
the advantage of maintaining data integrity)?
When the second instance tries to read from the row, will
the container make it wait till the row has been released OR throw an
exception ??
Thanks for your time.
Ashutosh.
----- Original Message -----
From: "Carlos Otero Barros" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 30, 2001 1:19 PM
> Hi.
> Not sure what you mean by "SELECT FOR UPDATE".
> Two instances of the same Entity Bean over the same row still have
different
> transaction contexts.
> You may expect isolation from transactions so you can rely on them.
> If two users try to update the row almost at the same time from different
> instances of the same class of Entity Bean then the standard transaction
> approach applies.
>
> Regards.
>
> ----- Original Message -----
> From: "manishi tuli" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 30, 2001 7:53 PM
>
>
> > if 2 instances of ejb are trying to update same row , can we handle this
> > thing with ejb transaction or we have to do with select for update
> >
> > thanks
> >
_________________________________________________________________________
> > Get Your Private, Free E-mail from MSN Hotmail at
http://www.hotmail.com.
> >
> >
>
===========================================================================
> > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> > of the message "signoff EJB-INTEREST". For general help, send email to
> > [EMAIL PROTECTED] and include in the body of the message "help".
> >
> >
>
>
===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
