> 1. MVCC semantics.  If we can't keep MVCC then the deal's dead in the
> water, no question.  Vadim's by far the best man to look at 
> this issue; Vadim, do you have time to think about it soon?

I'll comment just after weekends...
But Mike Mascari raised up very interest issue about am I *allowed* to
view the code at all. If we'll decide to continue with our own
smgr+WAL I'll not be able to free my mind from what I've seen
in SDB code. So..?
Ok, I'll read API documentation first...

Vadim


Wed, 17 May 2000 10:32:43 -0700
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM>
RE: Berkeley DB license 
At 10:32 AM 5/17/00 -0700, Mikheev, Vadim wrote:

> But Mike Mascari raised up very interest issue about am I *allowed* to
> view the code at all. If we'll decide to continue with our own
> smgr+WAL I'll not be able to free my mind from what I've seen
> in SDB code. So..?

Berkeley DB implements a write-ahead log and two-phase locking using
well-known techniques from the literature (see, eg, Transaction
Processing by Gray et al).  Hell, I've seen the server code for
Teradata, Illustra, and Informix, and have managed to make a living
in the industry for fifteen years anyway.

					mike


Wed, 17 May 2000 11:21:41 -0700
"Michael A. Olson" <mao@sleepycat.com>
RE: Berkeley DB license 