The recommended approach to the none-of-the-above exception?

  • Thread starter Thread starter apa
  • Start date Start date
A

apa

There are a few well-known (?) guidelines to throwing/creating exceptions
(paraphrasing my understanding of it):
1. Don't throw general types like Exception or ApplicationException.
2. Use existing exception classes where it makes sense (ArgumentException
etc).
3. Don't create custom exception types if they don't add anything of value.
(Value can be just being able to catch that exception and nothing else.)

However, where I get confused is where I don't have any specific information
to add about an exception, and don't expect any special exception handling
to occur. For example, say I do a database query, which very unexpectedly
returns an empty result set. I basically just want to

throw new Exception("no data from db");

FxCop will have issues with that though. Should I create a
"MyApplicationException" for the none-of-the-above stuff? It seems to break
rule #3.

Thanks!
 
apa said:
There are a few well-known (?) guidelines to throwing/creating exceptions
(paraphrasing my understanding of it):
1. Don't throw general types like Exception or ApplicationException.
2. Use existing exception classes where it makes sense (ArgumentException
etc).
3. Don't create custom exception types if they don't add anything of value.
(Value can be just being able to catch that exception and nothing else.)

However, where I get confused is where I don't have any specific information
to add about an exception, and don't expect any special exception handling
to occur. For example, say I do a database query, which very unexpectedly
returns an empty result set. I basically just want to

throw new Exception("no data from db");

FxCop will have issues with that though. Should I create a
"MyApplicationException" for the none-of-the-above stuff? It seems to break
rule #3.
Click to expand...

No, because of the bit in brackets - the type itself (e.g.
MissingDataException) would be useful information. You don't even need
to explicitly catch it for it to be of use - you might choose to break
into code when debugging as soon as that is thrown.

If it feels a bit specific to you, think about an exception which you
can use whenever the database is in an unexpected state -
"UnexpectedDatabaseStateException" or something similar.
 
Back
Top