Tuesday, October 30, 2001 01:06 PM
We are developing the intranet based application. I required to maintain the concurrency, currently we have implemented the currency using the SELECT .. FOR UPDATE clause of oracle. Using that way the row get locked in if the browser get crashed or machine re boot the same user will not be able to update the same record untill his/her session timed out. So what are the other most effiecient way to maintain the currency without row locking. Anybody has experience about the Oracle Transaction isolacation level Serialization to handle the concurrency. we tried but its not working as per the logically expected way.