Re: (Mis)use of transactions
- From: RedGrittyBrick <redgrittybrick@xxxxxxxxxxxxx>
- Date: Mon, 01 Oct 2007 14:20:22 +0100
Arne Vajhøj wrote:
RedGrittyBrick wrote:
Arne Vajhøj wrote:
I think you should drop database builtin locking and go to
application based locking.
Search for optimistic locking and pessimistic locking.
There are well known techniques to handle database operations
in human time (minutes) instead of computer time (milliseconds).
My Google-fu appears to be weak today. I just get lots of refs to EJB locking, Apache Object-relational-bridging etc. These don't appear to be what you are referring to :-(
I may have been a bit too optimistic.
:-(
http://c2.com/cgi/wiki?OptimisticLocking
http://c2.com/cgi/wiki?PessimisticLocking
http://martinfowler.com/eaaCatalog/optimisticOfflineLock.html
http://martinfowler.com/eaaCatalog/pessimisticOfflineLock.html
http://www.javaworld.com/javaworld/jw-01-2006/jw-0130-pojo.html?page=6
say something, but I must admit that it is far from clear
what they really mean.
If you can get your hands on a copy of Fowlers book, then
it has examples in Java/JDBC.
Many thanks :-)
.
- References:
- Re: (Mis)use of transactions
- From: Arne Vajhøj
- Re: (Mis)use of transactions
- Prev by Date: Re: Derby eclipse install
- Next by Date: Re: [Aaron J Tarter] Re: [comp.lang.java.databases] Derby eclipse install
- Previous by thread: Re: (Mis)use of transactions
- Next by thread: Re: Derby eclipse install
- Index(es):
Relevant Pages
|
