Path: news.easynews.com!easynews!news.he.net!cyclone-sf.pbi.net!64.42.15.2!HSNX.atgi.net!logbridge.uoregon.edu!tethys.csu.net!nntp!sn-xit-05!sn-xit-06!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: Sybrand Bakker Newsgroups: comp.databases.oracle.tools Subject: Re: PL-SQL: Exception NO_DATA_FOUND or %NOTFOUND Date: Sun, 07 Jul 2002 16:57:43 +0200 Organization: Posted via Supernews, http://www.supernews.com Message-ID: Reply-To: postbus@sybrandb.demon-verwijderdit.nl References: <3d259174$1@news.wau.nl> X-Newsreader: Forte Agent 1.91/32.564 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: newsabuse@supernews.com Lines: 40 Xref: easynews comp.databases.oracle.tools:52256 X-Received-Date: Sun, 07 Jul 2002 07:55:41 MST (news.easynews.com) On 7 Jul 2002 06:49:39 -0700, Thomas Kyte wrote: >incorrect. > > open c; > fetch c into ...; > if c%notfound then ..... > >the above code makes sense and properly detects the no data found condition >whereas: > > open c; > begin > fetch c into ...; > exception > when no_data_found then ..... > end; > >won't "work" -- it's a bug in the code. It'll never ever detect that "no data >was found" since the no_data_found exception is raised only when you use a >SELECT INTO. I did differentiate between exception and condition, did I? I never said a FETCH INTO raises the NO_DATA_FOUND exception, did I? Maybe I shouldn't have used the phrase 'raise condition' You could also argue about 'night and day different' In *both* cases sqlnet on the client side receives the ora-1403 error message. And it has always mightily suprised me error messages are being sent from server to client *in full*, as you will *always* get ora-1403, either expected or unexpected. Looks a waste of resources to me. But then we are probably both nitpicking. Regards Sybrand Bakker, Senior Oracle DBA To reply remove -verwijderdit from my e-mail address