Path: utzoo!attcan!uunet!lll-winken!csustan!csun!csusac!unify!rk
From: rk@unify.UUCP (Ron Kuris)
Newsgroups: comp.databases
Subject: Re: Selecting a commercial RDBMS (Request for suggestions)
Message-ID: <847@unify.UUCP>
Date: 25 May 89 14:35:15 GMT
References: <3199@tank.uchicago.edu> <2335@laidbak.UUCP> <13661@ncoast.ORG>
Reply-To: rk@unify.UUCP (Ron Kuris)
Organization: Unify Corporation, Sacramento, CA, USA
Lines: 33


In article <13661@ncoast.ORG> allberry@ncoast.ORG (Brandon S. Allberry) writes:
> As quoted from <2335@laidbak.UUCP> by egn@laidbak.UUCP (E. G. Nadhan):
> +---------------
> | In article <3199@tank.uchicago.edu> cs_bob@gsbacd.uchicago.edu writes:
> | >I don't know much about Unify,
> | >but the other three pre-process 3GL programs. 
> | 
> | 	Unify pre-processed 3GL programs too like the other three -- 
> | 		INGRES, ORACLE and INFORMIX.
> +---------------
> 
> Only if you use Unify's ESQL product, which didn't exist before Unify 3.2.
> *All* versions of Unify (well, "old" Unify; don't know about Unify 2000)
> have direct HLI functions callable from C.  !!!NOTE!!!  Unify HLI functions
> are NOT SQL-related!
With UNIFY 2000, a new set of RHLI calls are available.  These calls are
access method independent.  Of course, there are compatability archives for
HLI users available as well.  I may be mistaken, but I believe preprocessing
of UNIFY 2000 programs is only necessary if you want to do compile time name
binding, rather than runtime name binding.  A new ucc is still provided, which
does all the "preprocessing" almost transparently anyways.

In summary, even Unify 2000 has RHLI functions callable from C.

I may be slightly wrong here because I'm primarily working with 4.0/1.4
and later releases of this product here at Unify.  If you want to know for
sure, send email and I'll route it to a U2000 authority :-).

-- 
Ron Kuris		(916) 920-9092
rk@unify.UUCP
{{ucdavis,csun,lll-crg}!csusac,pyramid,sequent}!unify!rk