Re: min(); never no_data_found
From: Jeremy <jeremy0505_at_gmail.com>
Date: Wed, 23 Dec 2009 15:10:29 -0000
Message-ID: <MPG.259c434068c679ae9897b4_at_News.Individual.NET>
In article <79bb2ee5-f28a-43b9-af1e-4597012495f0 _at_a32g2000yqm.googlegroups.com>, Mark.Powell2_at_hp.com says...
Date: Wed, 23 Dec 2009 15:10:29 -0000
Message-ID: <MPG.259c434068c679ae9897b4_at_News.Individual.NET>
In article <79bb2ee5-f28a-43b9-af1e-4597012495f0 _at_a32g2000yqm.googlegroups.com>, Mark.Powell2_at_hp.com says...
>
> Cate, why not test for a NULL value being returned and if so the RAISE
> NO_DATA_FOUND?
>
What's the opinion of this ng's contributors on the advisability of raising "standard" error conditions when the underlying reasons for raising that error are different?
To me it seems like a practice not to be recommended - potential for misleading people unfamiliar with the code later on in maintenance mode.
-- jeremyReceived on Wed Dec 23 2009 - 09:10:29 CST