durusmail: durus-users: Durus basics
OODB basics
2005-10-08
Oleg Broytmann
2005-10-09
David Binger
2005-10-09
David Binger
2005-10-09
Oleg Broytmann
2005-10-09
David Binger
2005-10-09
Oleg Broytmann
2005-10-09
Oleg Broytmann
2005-10-09
mario ruggier
2005-10-09
David Binger
2005-10-09
David Binger
2005-10-11
mario ruggier
2005-10-12
Matthew Scott
Re: OODB basics
2005-10-11
Michael Watkins
OODB vs SQL
2005-10-09
Oleg Broytmann
2005-10-09
Oleg Broytmann
2005-10-09
Oleg Broytmann
Re: OODB vs SQL
2005-10-10
Michael Watkins
Re: OODB vs SQL
2005-10-10
Michael Watkins
OT: Durus
2005-10-13
Oleg Broytmann
2005-10-13
David Binger
2005-10-13
Oleg Broytmann
2005-10-09
John Miller
2005-10-09
David Binger
2005-10-09
Oleg Broytmann
2005-10-10
David Binger
2005-10-11
mario ruggier
2005-10-11
A.M. Kuchling
2005-10-11
Roger E. Masse
2005-10-11
Roger E. Masse
Re: OODB vs SQL
2005-10-11
Michael Watkins
2005-10-11
Michael Watkins
2005-10-11
David Binger
2005-10-12
Michael Watkins
2005-10-12
mario ruggier
2005-10-12
Michael Watkins
Demo application [was: Re: [Durus-users] Re: OODB vs SQL]
2005-10-13
mario ruggier
Re: OODB vs SQL
2005-10-11
Michael Watkins
Durus basics
2005-10-09
Oleg Broytmann
2005-10-09
David Binger
2005-10-10
Oleg Broytmann
2005-10-10
David Binger
2005-10-10
Oleg Broytmann
2005-10-13
Oleg Broytmann
2005-10-13
David Binger
2005-10-13
Oleg Broytmann
2005-10-13
mario ruggier
Re: OODB basics
2005-10-13
Oleg Broytmann
Durus basics
David Binger
On Oct 10, 2005, at 3:41 AM, Oleg Broytmann wrote:

>
>> That's not what you want.  Durus doesn't provide counters.
>> That would be provided by an application-level object.
>>
>
>    The problem is that application is on the client side, and there
> are a
> few forked processes, and there is no locking on the server-side.

The transactions act like locks.  The process that completes a
commit has, in effect, been holding a lock on the objects it changed.


reply