Xref: utzoo comp.lang.c++:9761 comp.object:1888 comp.databases:7371
Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!bg0l+
From: bg0l+@andrew.cmu.edu (Bruce E. Golightly)
Newsgroups: comp.lang.c++,comp.object,comp.databases
Subject: Re: C++ and INGRES
Message-ID: <Mb1shWK00WBLI22FR_@andrew.cmu.edu>
Date: 1 Oct 90 18:30:58 GMT
References: <7797@star.cs.vu.nl>
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 17
In-Reply-To: <7797@star.cs.vu.nl>

I don't see why not. One of the fundamental assumptions is that embedded
DMLs are transparent to the host language. SQL in particular is supposed
to be portable from language to language, so that an EXEC SQL ... remains
the same wether you're using COBOL, C or whatever. 

One of the things that makes this possible is that Ingres uses a
pre-processor to handle the DML. Thus, the SQL instructions are processed
into a form compatible with the host language BEFORE the compiler ever sees
the program.

Of course, you should be aware that Ingres does not presently support
objects very well at this point. They have something they call "user
defined data types", but these are quite the same thing. This is the
point at which
an attempt to embed DML in C++ might break down.

Good luck and good hunting...