From: Greg Pasquariello <gpasq@dbintellect.com>
Subject: Pro*C Cursor names and scope (was Re: OCI vs. Pro*C)
Date: 1996/02/22
Message-ID: <312CF313.6244@dbintellect.com>#1/1
references: <NEWTNews.823077819.3828.hpaiss@hadar.netvision.net.il>  <4d8s4i$msf@jake.probe.net>  <james.lawrence.154.00097BB4@epamail.epa.gov> <513768446wnr@kheldar.demon.co.uk> <4gaspk$hqj@inet-nntp-gw-1.us.oracle.com>
to: Scott Urman <surman@oracle.com>
content-type: text/plain; charset=us-ascii
organization: dbINTELLECT Technologies
mime-version: 1.0
newsgroups: comp.databases.oracle
x-mailer: Mozilla 2.0 (WinNT; I)


Scott Urman wrote:
> 
> In article <513768446wnr@kheldar.demon.co.uk>, Clint Redwood <clint@kheldar.demon.co.uk> writes:
> |> It also depends on what language you want... C or C++.
> |>
> |> Pro*C cannot handle c++ code... so you have to build all your oracle interaction
>                        ^^^
> This used to be true, but starting with Pro*C 2.1 (Oracle 7.2) we officially
> support embedding SQL in C++ code.

Can anyone tell me if cursor names can be used outside of the scope of
the file in 2.1?  In the version I have, cursor names can only be used
within the "precompilation unit", which prevents me from writing an
interpreter in C++ that implements an Execute followed by a Fetch in the
interpreted language.

Thanks for any information.  If you can, please email a response as I
don't have the bandwidth to check this newsgroup all the time.

-Greg


-- 
Greg Pasquariello
Chief Architect, dbINTELLECT Technologies
gpasq@dbintellect.com

This is precisely the kind of thing no one ever believes!