• Post Reply Bookmark Topic Watch Topic
  • New Topic

(Solved) Can clientB see changes clientA made before clientA releases lock?  RSS feed

 
Colin Yates
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Suppose clientA locks recordA. ClientA then updates (or deletes whatever) recordA. Before clientA releases the lock, clientB reads that record.

The URLyBird spec does not prevent this, but it is ambiguous about what clientB should see. Should clientB see the original record, the deleted record etc.?

Effectively, should we treat lock() as a semi-transacation, and unlock() as a commit? The spec doesn't imply this, but surely common-sense does?

What do you guys thing?

Col
[ February 25, 2005: Message edited by: Colin Yates ]
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Posts: 12152
256
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Col,

You might be interested in the topic "Why are dirty reads ok?.

My personal view is that, in the situation you describe, clientB will not see any record at all (that is - it will read the deleted record, and deleted records cannot be seen).

Regards, Andrew
 
Colin Yates
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Andrew.

So the consensus seems to be that there is no concept of a transaction.

Thanks again.

Col
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!