Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Record Locking in URLyBird

 
Marcelo Ortega
Ranch Hand
Posts: 528
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When a method performs a record lock, does it actually perform the lock on the db file or ONE record only? If the answer is this last one, how is this possible?

Please comment, thanks.
[ September 26, 2005: Message edited by: Marzo Kaahn ]
 
Marcelo Ortega
Ranch Hand
Posts: 528
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am understanding a little more now; is the basic concept the following, or am i still missing something:

Any client can READ the db file - so we can't lock the whole file. What we actually lock is the NUMBER of a specified record which is held in some sort of collection?

Is this correct?

Any futher clarification will be more than welcome.
 
Marcelo Ortega
Ranch Hand
Posts: 528
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I feel as if i am talking to myself here. Accoring to the specs:


You may assume that at any moment, at most one program is accessing the database file; therefore your locking system only needs to be concerned with multiple concurrent clients of your server.


i beleive we can lock the actual file?

Please clear this up, someone, anyone.


[ September 26, 2005: Message edited by: Marzo Kaahn ]
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 12014
220
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Marzo,

I assume you are talking about the locking that occurs when a client calls the Data lock() method?

In which case you are performing a logical record lock on an individual record. You are not performing a physical lock on the record or the file.

What you should be trying to achieve is setting up a situation where, after one client logically locks a record, no other client can logically lock the same record, however other clients can obtain logical locks on other records, and file operations can still occur.

Regards, Andrew
 
Marcelo Ortega
Ranch Hand
Posts: 528
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Andrew, i see what your saying. Still waiting for your book
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic