agora inbox for postgres@postgres.berkeley.edu
help / color / mirror / Atom feedFrom: Paul M. Aoki <aoki@postgres.Berkeley.EDU>
To: Mark Metson <gpurdy@fox.nstn.ns.ca>
Cc: postgres@postgres.Berkeley.EDU
Subject: Re: Use by a Business
Date: Mon, 30 May 94 12:40:03 -0700
Message-ID: <199405301940.MAA19840@faerie.CS.Berkeley.EDU> (raw)
In-Reply-To: <Pine.3.89.9405300812.B357-0100000@acamn.aca.uucp>
Mark Metson <gpurdy@fox.nstn.ns.ca> writes:
> If I utilise postgres instead of Business Basic to rewrite the
> package, where would we stand regarding postgres license?
Permission to use, copy, modify, and distribute this software and its
documentation for educational, research, and non-profit purposes and
without fee is hereby granted, provided that the above copyright
notice appear in all copies and that both that copyright notice and
this permission notice appear in supporting documentation, and that
the name of the University of California not be used in advertising
or publicity pertaining to distribution of the software without
specific, written prior permission. Permission to incorporate this
software into commercial products can be obtained from the Campus
Software Office, 295 Evans Hall, University of California, Berkeley,
Ca., 94720. The University of California makes no representations
about the suitability of this software for any purpose. It is
provided "as is" without express or implied warranty.
offhand, i'd say if someone's making money from the construction
of a system, you should talk to the licensing people (just to be
safe).
personally, i would not sell a package to a client that contained
postgres (or university ingres, for that matter -- i once told the
last ingres chief programmer about a product that had ingres89
embedded in it and his reaction was priceless). i'd get a
commercial database. (but then, i'm the sort of person who'd say
that if my paycheck was on the line, i'd use bsd/386 instead of
linux, too.. i like linux, but.. :-)
> Primarily we
> need record-locking; it appears ingres and metalbase do not provide this
> (at least for isam type databases) whereas postgres does.
nope, postgres doesn't do record locking either. it does actually
have a multilevel escalating lock manager built in, but it isn't
used at the record level. it does do page-level locking for b-trees
but not for r-trees and heaps.
(montage has page-level locking for heaps.)
--
Paul M. Aoki | CS Div., Dept. of EECS, UCB | aoki@postgres.Berkeley.EDU
| Berkeley, CA 94720 | ...!uunet!ucbvax!aoki
==============================================================================
To add/remove yourself to/from the POSTGRES mailing list: send mail with
the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"
If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
a human will deal with it. DO NOT post to the "postgres" mailing list.
==============================================================================
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: postgres@postgres.berkeley.edu
Cc: aoki@postgres.Berkeley.EDU, gpurdy@fox.nstn.ns.ca
Subject: Re: Use by a Business
In-Reply-To: <199405301940.MAA19840@faerie.CS.Berkeley.EDU>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox