Pessimistic Locking: they need to be removed once the transaction completes

dezbyte / multiverse

Automatically exported from code.google.com/p/multiverse

Other

0 stars 0 forks source link

Pessimistic Locking: they need to be removed once the transaction completes #59

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

All locks hold by a transaction should be removed as soon as the
transaction completes.

Original issue reported on code.google.com by alarmnum...@gmail.com on 22 Mar 2009 at 12:41

GoogleCodeExporter commented 8 years ago

At the moment only locks on objects that are dirty are released because the 
commit
only knows about these objects for releasing locks.

Optimization:
The lock information is stored inside the transaction, so would not be a 
problem to
access that to release the locks.

Original comment by alarmnum...@gmail.com on 22 Mar 2009 at 12:48

GoogleCodeExporter commented 8 years ago

Original comment by alarmnum...@gmail.com on 2 May 2009 at 10:21

Added labels: backlog
Removed labels: 0.2

GoogleCodeExporter commented 8 years ago

Original comment by alarmnum...@gmail.com on 4 May 2009 at 8:37

Changed title: Pessimistic Locks need to be removed once the transaction completes

GoogleCodeExporter commented 8 years ago

Original comment by alarmnum...@gmail.com on 4 May 2009 at 8:39

Changed title: Pessimistic Locking: they need to be removed once the transaction completes

GoogleCodeExporter commented 8 years ago

Original comment by alarmnum...@gmail.com on 19 May 2009 at 5:17

Added labels: Type-Enhancement
Removed labels: Type-Defect