Pessimistic Locking: Configurable acquire on encountered instead of on commit

dezbyte / multiverse

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

Other

0 stars 0 forks source link

Pessimistic Locking: Configurable acquire on encountered instead of on commit #29

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

Just like oracle, when an object is updates, the object is automatically
locked exclusively for the duration of the transaction.

The 'problem' is that adding a pessimistic lock the the object
automatically, requires additional instrumentation to check for updates and
this could be a performance problem. 

I'm not sure if this feature really is needed.

Original issue reported on code.google.com by alarmnum...@gmail.com on 14 Dec 2008 at 8:31

GoogleCodeExporter commented 8 years ago

Original comment by alarmnum...@gmail.com on 5 Feb 2009 at 12:48

Added labels: backlog
Removed labels: 0.5

GoogleCodeExporter commented 8 years ago

It could be done optional perhaps.. using some kind of annotations maybe.

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

Changed title: Pessimistic Lock: Acquire when encountered instead of on commit

GoogleCodeExporter commented 8 years ago

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

Changed title: Pessimistic Locking: Acquire when encountered instead of on commit

GoogleCodeExporter commented 8 years ago

Original comment by alarmnum...@gmail.com on 20 May 2009 at 6:10

Changed title: Pessimistic Locking: Configurable acquire on encountered instead of on commit