Re: Cursor in PL/SQL

The columns will all be fetched into a single records a row at a time, so there's no significant memory problems involved with a large number of rows.

Adding the SELECT...INTO would be a significant performance drain, and would likely use more memory than a simple cursor for loop.

Jared

On Mon, 22 May 2000, Troiano, Paul (CAP, GEFA) wrote:

>
> I am writing a PLS/SQL procedure that needs to deal with a table with 100
> columns. All 100 columns are needed and there can be anywhere from 5 to
> 10,000 records to be dealt with at a time. Is it better to create a cursor
> with all 100 fields and then deal with them? Or, is it better to create the
> cursor with just the primary key and use a SELECT ... INTO, for all 100
> fields, as needed?
>
> Why?
>
> Thanks,
>
> - Paul
> --
> Author: Troiano, Paul (CAP, GEFA)
> INET: Paul.Troiano_at_gecapital.com
>
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from). You may
> also send the HELP command for other information (like subscribing).
>

Jared Still
Certified Oracle DBA and Part Time Perl Evangelist ;-) Regence BlueCross BlueShield of Oregon
jkstill_at_bcbso.com - Work - preferred address Received on Mon May 22 2000 - 18:05:26 CDT