Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: pro*c, multiple execution of SELECTs

Re: pro*c, multiple execution of SELECTs

From: Torsten Mueller <dev-null_at_shared-files.de>
Date: Thu, 09 Jun 2005 11:33:34 +0200
Message-ID: <uslzrub69.fsf@fastmail.fm>


sybrandb_at_yahoo.com schrieb:

> There is not.

:(

I saw some expamples now in the pro*c Programmer's Guide that also do not have any statement between SELECTs.

> However the use of the AT syntax is unnecessary when connecting to only
> one database.

I have two connections but I assume they do not disturb each other.

> To get proper help however, your usage of the verb crash is too
> unspecific and calls for the use of a crystal ball.

The verb "crash" means just an "unexpected indeterministic program termination" in an Oracle library function. The program execution dives into the function and does not come out anymore until the program terminates with a core dump.

I can add still the following informations:

- The program does not use cursors and explicit fetching at all.
- The SELECTed data are stored into host variable arrays.
- The SELECT with it's WHERE clause leads to just one single row.
- The host variable arrays can hold 10 rows.
- All the physical variables in the host variable arrays are large
  enough according to the size of the columns. - NULL values are handled using indicator variables. - The indicator variables are "short" (this means 16bit).

T.M. Received on Thu Jun 09 2005 - 04:33:34 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US