• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Use of Lock/Unlock with local client/db access!

 
Abhinav Chandra
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What is the use of Lock/Unlock when you are running both client and database locally - I mean there cannot be more than one client locally so do we need Lock/Unlock in that case.
 
Cleland Early
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Don't sweat it, I say. I don't think it hurts anything to use the lock code when you're in local mode.
 
Emerson Dunne
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree. I've seen posts from people who implemented their database locking logic based on the local/remote connection modes of their data clients.
The database should not care what connection mode the database client is operating in. So your database locking/unlocking logic shouldn't concern itself with such things.
Now if the data client code wants to call lock & unlock differently based on the connection mode, that's fine... but probably un-needed and creates more code to test, maintain, document and risk introducing bugs.
 
Abhinav Chandra
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanx guys, for the advise. It seems like I should do lock/unlock no matter whether I am using local client access or networked access - for simplicity sake!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic