Databases
StackOverflow2013
Postsdbo
POIs it normal to use many business exceptions if needed?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs it normal to use many business exceptions if needed?
    primarykey
    data
    text
    <p>Is it a good practice to define and throw custom exceptions even if the application needs lots of them?</p> <ul> <li>EntityNotFoundException</li> <li>EntityAlreadyExistsException</li> <li>EntityNotUniqueException</li> <li>EntityNotAddedException</li> <li>EntityNotUpdatedException</li> <li>EntityNotDeletedException</li> <li>QuizOverException</li> <li>QuizExpiredException</li> <li>TableAlreadyBookedException</li> <li>EndDateMustBeGreaterThanStartDateException</li> </ul> <p>I tried to name these sample exception names to describe their purpose as good as I could. I hope they could form an idea of what I am trying to ask.</p> <p>Don't limit your imagination with only these exceptions but all that could arise during you application's life. Consider both CRUD and business exceptions.</p> <p>I know that throwing and catching exceptions is an expensive process in terms of performance but don't they provide a more elegant way to develop you app?</p> <ul> <li>Isn't it better to throw a <code>EntityNotFoundException</code> instead of writing an if statement to check whether the entity is null?</li> <li>Isn't it better to throw a <code>EntityAlreadyExistsException</code> instead of writing an additional if statement which will call a method to check whether the entity with the given Id already exists?</li> <li>Isn't it better to throw a <code>EntityNotAddedException</code> instead of checking the return value of type bool specifying whether the transaction was successful or not? What if we want to return an object?</li> </ul> <p>I feel that the answer will be like "you should not use <code>EntityNotFoundException</code> but instead check if null, but you should use <code>EntityAlreadyExistsException</code>", "there is no holy grail".</p> <p>I am wondering what is the elegant way of doing this?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USanar khalilov
    1. USanar khalilov
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs it normal to use many business exceptions if needed?
      1. USanar khalilov
      1. VTBountyStart
    2. VO
      singulars
      1. POIs it normal to use many business exceptions if needed?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf the application needs lots of custom exceptions, then it is good practice to define and throw lots of custom exceptions, simply because it's the only way. If there were another way than to define and throw lots of custom exceptions, the application does not need lots of custom exceptions.
      singulars
      1. POIs it normal to use many business exceptions if needed?
      1. USOswald
    2. COIf you are planning to throw multiple exceptions then, I am assuming, you must be planning to catch them all in multiple catch blocks as well. Whatever your decision on your question is, IMO at the end put a generic catch(Exception ex) kind of block as well so that you do not miss out on catching any exception which you might not have thought of. Of course code that part carefully and gracefully.
      singulars
      1. POIs it normal to use many business exceptions if needed?
      1. USsamar
    3. CO@samar "*IMO at the end put a generic `catch (Exception ex)` kind of block as well*" - not good advice. The point is you only catch the exceptions which you *know* you can handle, everything else should bubble up and kill the application because it's now *technically* in a corrupt state.
      singulars
      1. POIs it normal to use many business exceptions if needed?
      1. USJames
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload