Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!rice!uupsi!pbs.org!mhunt From: mhunt@pbs.org Newsgroups: comp.databases Subject: Re: Why is Oracle better than Ingres Message-ID: <1990Nov30.144440.10878@pbs.org> Date: 30 Nov 90 19:44:40 GMT References: <734@keele.keele.ac.uk> <142@genco.bungi.com> Organization: PBS:Public Broadcasting Service, Alexandria, VA Lines: 59 In article <142@genco.bungi.com>, rad@genco.bungi.com (Bob Daniel) writes: > In article <734@keele.keele.ac.uk> csb19@seq1.kl.ac.uk (K. Allen) writes: > >In article <734@keele.keele.ac.uk> csb19@seq1.kl.ac.uk (K. Allen) writes: >>Could someone outline the major differences between Oracle and Ingres. >>Please state if you are using the commercial or university versions >>of Ingres. >> > >I work with Oracle, not Ingres but know someone using Ingres. Oracle >recovers very well from crashes where I hear Ingres can completely >crash the database if the system crashes. In the seven years that I've worked with commercial versions of Ingres, I have never lost any data due to a system crash. I will say that prior to Ingres 6.0, database inconsistencies may have occurred as a result of a crash. However, I never experienced a situation where I could not recover the database using the Ingres RECOVERDB utility. > >Ingres seems to be more 'developer' friendly than Oracle's SQL Forms 3.0. >If you are developing entirely in C and not using a front end, Oracle is a >very nice database engine. I give Oracle's database engine an 'A'. SQL Forms >3.0 isn't entirely bad depending on the application your writing. I've >worked with better front ends though (4th Dimension on Mac). It's true that Ingres is 'developer' friendly, which will usually result in more productive developers and friendlier end-user applications. I think that it's a little impractical to pay a considerable amount of money for RDBMS and not make use of its developer's toolkit (SQL*Forms). Along with providing a extremely powerful database engine, Ingres' Visual Forms Editor (VIFRED) is a comprehensive and easily understood method of developing the front-ends for your applications. Other Ingres options worth noting: Knowledge Management o Rules o Stored DB Procedures Object Management o User-Defined Data Types (UDTs) - Allows you to develop your own abstract datatypes that can be used in your applications like any of the standard Ingres datatypes. o User-Defined Functions (UDFs) - Allows you to develop functions that can be linked to the Server and used with SQL statements. -- mhunt@pbs.org