Re: how does a dbms manage long-lasting transaction?

Sven Till wrote:

> A "long-lasting" also called "long-term" transaction is for me a
> transaction where you have to lock a object for a quite long time. let
> say some hours or day(s).
> I heard about it but I could not find material and further information.
> It seems that someone uses such kind of transaction during the
> development of software or of integrated circuits.
>
> Thx. in advanced for your help
>
> Sven
>

Rick Catell's book on Object Data Management is good but basically the answer is versioning. Versions are made public (if there are no conflicts) or left private but versions can be made without the fear of deadlocks or conflicts.

>
> Todd Gillespie wrote:
> >
> > Sven Till <sven.till_at_gmx.net> wrote:
> > : I am looking for information how databases manage long-lasting
> > : transaction.
> > <snip>
> > : Or is there no difference between the managing of a quite short
> > : transaction or long-lasting one?
> >
> > Could you define a long-lasting transaction for us?
Received on Fri Sep 07 2001 - 07:22:35 CEST