This is really a database issue. If your database supports column level
locking, you could get away with this. Otherwise, you will have to rely on
the row or page level lock.
Jonathan Baker
Internet Applications Division
Sybase
Anupam Khandelwal wrote:
>
> Hi,
> I know only some particular columns will change their values in the cocurrent
> scenario... If I set Transaction_Serializable attribute, I might be locking the
> whole row/page depending on the database and locking mechanism used... Other
> transaction which just a read transaction, has to wait for the first transaction
> to be completed.. I need to set the first transaction serializable attribute
> because, it is updating some sensitive data and some other transaction should
> not intefere with it.. But the whole row need to be locked... In this scenario
> how can I do column locking..
>
> If someone can guide me, I would be really greatful..
>
> Thanks
>
> Anupam
>
> ===========================================================================
> 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".
