Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!ucsd!ucbvax!CHERRY.CRAY.COM!cargo
From: cargo@CHERRY.CRAY.COM (David S. Cargo)
Newsgroups: comp.lang.icon
Subject: Re: Icon as RDBMS report writer language
Message-ID: <9010031337.AA01510@cherry04.cray.com>
Date: 3 Oct 90 13:37:08 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 26

>Date: 2 Oct 90 21:09:13 GMT
>From: esquire!yost@nyu.edu
>Subject: Icon as RDBMS report writer language
>To: icon-group@arizona.edu
>Organization: DP&W, New York, NY
>
>Has anyone used Icon as the basis for a RDBMS report writer language?
>Such a beast could be soooo much better than some other things out there...
>
> --dave yost

I have used Icon as a part of a process for some data base publishing,
but only in conjunction with other programs.  Cray keeps a software
problem report data base using ORACLE.  My section in Cray likes to see
reports about our status weekly.  Using canned and dynamically
generated queries, I extract a formatted report that I then feed to an
Icon program for further processing.  The further processing in this
case means extracting data and rewriting it with LaTeX code and macro
calls defined in the tables.sty file.  The result is formatted with
LaTeX and printed with dvips on our Sun LaserWriters.

I have in some cases written PostScript directly from Icon programs,
but in this case it seemed a lot easier on me to let existing programs
shoulder the burden of doing the formatting.

dsc