Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!berlin
From: berlin@bu-cs.BU.EDU (David K. Fickes)
Newsgroups: comp.databases
Subject: INGRES/EQC and SQL/C ...and general notes...
Summary: nested equel statements...
Keywords: ARGGGH!
Message-ID: <24546@bu-cs.BU.EDU>
Date: 24 Aug 88 20:45:21 GMT
Reply-To: berlin@buita.bu.edu (David Fickes- Einstein Project)
Organization: Boston University - Einstein Papers Project
Lines: 36

We're running INGRES 5.1 on our suns and I'm doing a bit 
of programming using EQUEL/C ... Someone has suggested that our
applications be written in SQL/C for "portability." Is this
simply a pipe dream or might it actually be possible to transfer
something written with the Ingres C / SQL preprocessor and move
it to another system using say.. Informix/C ?? 

One other question. What's so hard about supporting NESTED EQUEL
statements in the EQUEL/C processor???  I've got some code that looks like 
this:

## ingres "einstein"
## range of d is dukasfin3
## retrieve (c_uid=d.uid) where d.date=" " and
##      squeeze(d.doc_date)="00/00/??";
##{
##      retrieve (c_year=right(squeeze(d.doc_date),2)) where d.uid=c_uid;
##      replace d(date=date(01/01/c_year)) where d.uid=c_uid;
##}


Besides the basic point of .. "this could be done a WHOLE LOT BETTER" this
is a nice painless way of stating for each record that qualifies
change it to X...

But without the nesting you have to jump a few more loops.. it seems
to me to be a rather OBVIOUS feature thats been left out?  Why.. is
it a technically difficult thing to do .. or is RTI just not doing
the obvious?  

- david-- 
==============================================================================
David K. Fickes     Center for Einstein Studies/Einstein Papers Project
UUCP: ...harvard!bu-it!berlin			Boston University 
OTHERWISE: berlin@bu-it.bu.edu			745 Commonwealth Avenue
PHONE:	(617) 353-9249	(617) 277-9741		Boston, MA 02215