Re: Proposal: replace no-overwrite with Berkeley DB

>
>We could get perpetual rights to the code as integrated into our code. 
>Also, if they change something, we could always take it as our own and
>keep it working for us.  I think we would need something like that.
>

One of the often-stated virtues of PGSQL is that it is easy for a company
to take the source and go commercial. If you start integrating 'special
license greements' into the development, then that advantage is severly
reduced. 

A commercial operator has to form an agreement with sleepycat or rewrite
the storage manager. Unless sleepycat grant a completely open license to
PGSQL and all it's commercial descendants in perpetuity, it seems you may
be removing one of the seeling points of PGSQL.


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.C.N. 008 659 498)             |          /(@)   ______---_
Tel: +61-03-5367 7422            |                 _________  \
Fax: +61-03-5367 7430            |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/