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".
