Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!uwvax!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: <3305@tank.uchicago.edu>
Date: 18 May 89 15:55:21 GMT
References: <985@resource.UUCP> <309@viusys.UUCP> <24295@agate.BERKELEY.EDU> <1932@ssc.UUCP> <3295@tank.uchicago.edu> <24574@agate.BERKELEY.EDU>
Sender: news@tank.uchicago.edu
Reply-To: monty@delphi.UUCP (Monty Mullig)
Distribution: na
Organization: U. Chicago Computer Science Dept.
Lines: 19
Xref: utzoo comp.databases:2574 comp.lang.misc:2957 comp.software-eng:1543

Steve Goldfield writes:

	2. The Ingres Report-Writer reference manual states quite
	clearly, on page 4-8, "Only one .query command is permitted for a
	report, and only one data retrieval statement is permitted within the
	.query command." So, while that single retrieval statement may,
	presumably, join several tables, it didn't do me any good when I
	needed to append from two tables and then join from other tables. This
	restriction is a severe one.

Exactly what i said, one SELECT.  And, you're absolutely right, the
report writer is severely limited.  I end up going straight to ESQL/C
for anything remotely complex, and reserve the report writer for the
trivial reports.  I was only correcting the misunderstanding that the
report writer allows queries on only one table; I certainly wouldn't
try to do anything more than that, like defend the thing as a great
tool, it isn't worth that...

--monty