Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!labrea!decwrl!pyramid!voder!blia!forrest
From: forrest@blia.BLI.COM (Jon Forrest)
Newsgroups: comp.databases
Subject: Quality of Database Products
Message-ID: <3265@blia.BLI.COM>
Date: Fri, 11-Sep-87 13:35:07 EDT
Article-I.D.: blia.3265
Posted: Fri Sep 11 13:35:07 1987
Date-Received: Sat, 12-Sep-87 19:43:40 EDT
Organization: Britton Lee, Berkeley, CA
Lines: 26

There has been some discussion recently of the quality of several
RDBMS products, particularly Oracle. This reminds me of something
I've been wondering about for a while. I see Oracle, Ingres,
Sybase, and other systems coming out in many different operating
system environments. This makes lots of sense can't this is what
the market place demands. What concerns me is how such systems
are written to work in all these different environments. Specifically,
how much code is portable and how much has to be rewritten for each
environment? This is important because writing new code for each
environment increases the chances of bugs appearing.

One of the nice features I like about Britton Lee (which I'd like
even if I weren't an employee) is the fact that about 80% (a guess)
of our host software code is portable across all environments we
support. This means that the same code is used in all environments,
this descreasing the chances of bugs appearing. It also make the
software engineering work a lot easier.

I'd like to hear from other companies how they manage their
software in order to make it work in different software environments.
I'll be glad to describe how we do it.

Jon Forrest

ucbvax!mtxinu!blia!forrest
{pyramid|voder}!blia!forrest