Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you use exceptions for control flow, then you would want to stay away from policy-based exception handling.</p> <p>But in the case of exceptions which you want to treat as non-recoverable (a background task failed, the socket was disconnected, the file was deleted, etc.), you may want to have configurable, policy-based exception handling.</p> <p>For example, if you are developing an API, you may want to have every function in your API throw only the standard exceptions (<code>ArgumentException</code>, etc.), as well as your own library-specific exception in the case of an inner non-standard exception (e.g. a <code>MyLibraryException</code>). In this type of case, all that matters is that something did not work correctly. You are not picking apart the exception and figuring out what went wrong. You are simply acknowledging the fact that <em>some</em>thing went wrong, and that you are supposed to do <em>some</em>thing now.</p> <p>That <em>some</em>thing should be configurable, because it doesn't really matter what you do. Display a Message Box to the user? Modal or non-modal? Log the exception? How do you want to log the exception? Call a logging web service? Append to a log file? Write to the Windows Event Log? Insert an entry into the database? Insert an entry into two databases? It doesn't really matter to the rest of your application. The choice of how to handle an exception is completely orthogonal to the rest of the application.</p> <p>(As an aside, this is not how I would approach configurable policy-based exception-handling. I would tends more towards an AOP style, such as registering an exception-logger interceptor in the container.)</p>
    singulars
    1. This table or related slice is empty.
    1. POMicrosoft Exception Handling Block - Isn't it a perfect example for overengineering?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USyfeldblum
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMicrosoft Exception Handling Block - Isn't it a perfect example for overengineering?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI agree that you might want to configure what will happen (notify user, log exception, send email to support, etc.) before your application goes down anyway. You seem to refer to all the rest (swallow, rethrow, etc.) with "control flow", right?
      singulars
      1. PO
      1. USAndreas Huber
    2. CONot necessarily - it depends on the software. If you are treating exceptions as recoverable, then you are treating them as control flow. If you are treating them as non-recoverable, then you might be interested in this application block.
      singulars
      1. PO
      1. USyfeldblum
    3. COTreating an exception as recoverable would be something sending an Update statement to SQL Server if a corresponding Insert statement failed. That's control flow.
      singulars
      1. PO
      1. USyfeldblum
 

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