Bill,
If you are or will be retrieving more than say 1 rows, I'd say do not
use BULK COLLECT (performance goes down)... instead use a pl/sql table of
records. But I'd say even with the inconvenience of specifying a separate
collection for each column, use for BULK BINDS for
Title: RE: collections/PLSQL tables
Raj,
Well, you can limit the number of rows BULK COLLECT will return with the LIMIT keyword. Wouldn't that take care of the performance problem you refer to? And isn't it affected by the amount of free memory on the host? For insteance, there's very
Lisa,
you are right ... on both counts ... but look at it this way ... if you use
the LIMIT clause, when you go for fetch next set of data, you have to figure
out which rows to skip, so there you have more logic to work with.
As for the amount of memory, you are right too, but then again it
Title: RE: collections/PLSQL tables
Really? The documentation says that when you use limit, you won't have to keep track of records you have already used and haven't already seen. But then again the documentation has been wrong before. I'll have to give it a try.
Thanks for your comments Raj
