Xref: utzoo comp.databases:2570 comp.lang.misc:2955 comp.software-eng:1540
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!delphi!monty
From: monty@delphi.uchicago.edu (Monty Mullig)
Newsgroups: comp.databases,comp.lang.misc,comp.software-eng
Subject: Re: need help choosing between INGRESS and PROGRESS
Keywords: INGRESS, PROGRESS
Message-ID: <3295@tank.uchicago.edu>
Date: 18 May 89 14:05:24 GMT
References: <985@resource.UUCP> <309@viusys.UUCP> <24295@agate.BERKELEY.EDU> <1932@ssc.UUCP>
Sender: news@tank.uchicago.edu
Reply-To: monty@delphi.UUCP (Monty Mullig)
Distribution: na
Organization: U. Chicago
Lines: 22


fyl@ssc.UUCP (Phil Hughes) writes:

	In article <24295@agate.BERKELEY.EDU>, steve@violet.berkeley.edu
	(Steve Goldfield) writes:
	> I haven't used PROGRESS, but I can confirm the weakness
	> of Ingres' report writer.
	>
	> First of all, it is limited to a single retrieve

	Yuck.  This is not a problem with Progress.  How can you have a
	real relational database if you can't retrieve stuff from
	multiple tables?

well, now, wait a minute.  sure, ingres is disappointing in a number
of ways, but the idea that you can use only one table in the report
writer just isn't true.  what we have here, i think, is a failure to
communicate.  ingres allows only one SELECT statement in the report
writer, but of course that SELECT statement is a full featured SELECT
and can include joins to other tables.

--monty