Bug in SQL%rowcount, found, notfound, etc.?

[teado]

Greetings all,

I was discussing with my boss the reasons why I chose to use SQL%rowcount within a PL/SQL program. He mentioned that at one point, using the SQL%rowcount, found, and notfound functions were not consistent, nor 100% reliable. I looked around online (as well as here), but have not found any documentation suggesting this.
We're using Oracle 8.0.something, and soon 8.1.7(I think). Is the 'bug' described above true, either with our version or a previous version?
What I did find, which I knew, was that it can be easy to create a 'logic bug', and try to retrieve the rowcount, etc. for an 'old' SQL statement that since have been replaced with another SQL statement.

Thanks for any help. - Jeff

 

[rcurva]

I have no information of any bug related to these SQL attributes (rowcount, found, notfound). Maybe your boss knows better. Or we could wait for other replies if they have a knowlege of such bug.

Robbie

"The rule is, not to besiege walled cities if it can possibly be avoided" -- Art of War

 

[sem]

I have no such information, but bosses usually know better

 

[DavidCroft]

I've used these features for many years and never had any problems with them - perhaps you should ask your boss why he believes this is the case

 

[carp]

Concur. This has always worked correctly for me for years and I have never heard of them misbehaving.
Perhaps your boss had experience with code that misused these features.
Ask him where he got his information, since there's a very large user community that would LOVE to know the details!

 

[teado]

Thanks for the responses. My boss did say his experience was at a previous job, which would have been several years earlier. I suspect he might have had a logic bug and not realized it.

- Jeff