Recently came across Steven Feuerstein's article: http://www.oracle.com/technology/oramag/oracle/08-mar/o28plsql.html . After reading it, I realized that the simple fact is when using limit clause in the bulk collect, if one sets limint to be n, and if Oralce is unable to fetch n records from the cursor (even being able to fetch n-1 records), then Oracle will evaluate c%notfound to be TRUE. If I knew this fact, I could explain what I observed in my test case easily.
Thanks David for taking time to look at my question. You are absolutely correct to indicate the reason is my using c%notfound in the bulk collect loop (Steven's article also mentioned that it should not be used in such case at all), I am just not smart enough to get it . Denis --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Oracle PL/SQL" group. To post to this group, send email to Oracle-PLSQL@googlegroups.com To unsubscribe from this group, send email to oracle-plsql-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Oracle-PLSQL?hl=en -~----------~----~----~----~------~----~------~--~---
