jQuery in Action, 3rd edition
The moose likes JDBC and Relational Databases and the fly likes dirty read problem Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "dirty read problem" Watch "dirty read problem" New topic

dirty read problem

raj esh

Joined: Apr 03, 2010
Posts: 10
i have a jdbc code, which is fetching data from a table consists of lakhs of records and we are manipulating some values in table and these are posting into some other database(sap) and updating the record in our database as it is posted. but the problem is if we are running application from different servers(by mistake) the same reocrd is fetched in both applications, and manipulating and posting into sap database(this time posting twice)
i guess we have to set record level locking for this.how to set record level locking ?
can someone help me in this?
John Bengler
Ranch Hand

Joined: Feb 12, 2009
Posts: 133
Hi Banthi,

I'm not sure if this works for every database, but in Oracle you can use a "select for update", like described here:

Row Level Locking in JDBC

Just be sure to release your locks by commit/rollback when you're done..

I agree. Here's the link: http://aspose.com/file-tools
subject: dirty read problem
It's not a secret anymore!