Re: Q: How to talk directly to oracle?

In article <DL3xMs.722_at_news2.new-york.net> Terry Thorsen <terry_at_unix.asb.com> writes:
>From: Terry Thorsen <terry_at_unix.asb.com>
>Subject: Q: How to talk directly to oracle?
>Date: Sat, 13 Jan 1996 06:49:40 GMT
 

> I'm trying to find out the different ways to talk directly to Oracle on
> UNIX. I would like if anyone could disclaim what I have found out or
> eleborate on what is wrong or what is missing.
 

> Visigenic ODBC SDK - requires odbc driver. Not sure how this talks
> to SQL*net or to oracle without SQL*net.

SQLNet on the client side simply provides the same APIs that the database does. If you're on the same box as the database you don't need SQLNet, you can talk directly to the database. Any ODBC driver is just translating the ODBC API calls to the native database calls. I have seen some that do not need SQLNet but they have code on the database end that still talks to the native API, they're just taking care of the network part too.

> PRO*C - precompiler. Does this use libraries?
 

> OCI - Must use libraries but what do these libraries do? Do they
> set up their own session? Do they talk through SQL*Plus?

Both of these use the APIs. They do use some different calls. Both must 'connect' using a call before they can do anything else. Connecting establishes the session. Theoretically you don't have to buy anything from Oracle except the DB if you go OCI, with Pro*x you must buy the precompiler.

> Pipes to SQL*Plus - hmmm. Is this efficient? Is it standard?

Why??????

> Something about an SQL*Plus spool directory?
 

> dbtools.h - Not sure how this works but looks real nice.
 

> other "class libraries" - must work like dbtools.h

Anything is ultimately in the end going to end up talking to the database with the same calls.

> Advice is greatly appreciated,
> Terry Thorsen
> terry_at_unix.asb.com
Received on Wed Jan 24 1996 - 00:00:00 CET