Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'd like to suggest to you that if you do not know what to do with an exception, do not catch it. Too often, coders catch exceptions and just swallow them whole.</p> <pre><code>catch (Exception ex) { /* I don't know what to do.. *gulp!* */ } </code></pre> <p>Clearly this isn't good, because bad things are happening, and no action is being taken. Only catch exceptions that are actionable!</p> <p>That said, graceful error handling is important. Don't want your app to crash, right? You may find ELMAH useful for web applications, and a global exception handler is pretty easy to set up for WinForms or XAML desktop apps.</p> <p>Putting all that together, you might find this strategy useful: 1. catch specific exceptions that you know might occur (DivideByZeroException, SQLException, etc.) and steer away from the generic catch-all Exception; 2. re-raise the exception after you handle it. e.g.</p> <pre><code>catch (SQLException ex) { /* TODO: Log the error somewhere other than the database... */ throw; // Rethrow while preserving the stack trace. } </code></pre> <p>What can you really do with a SQLException? Did the database connection disappear? Was it a bad query? You probably don't want to add all the handling logic for that, and besides, what if it's something you didn't expect? So just handle the exception if you can, <strong>re-raise</strong> it unless you're certain it's resolved, and gracefully handle it at a <strong>global</strong> level (e.g. Show a message like "Something went wrong, but you might be able to continue working. Detailed info: '[ex.Message]'. Abort or Retry?")</p> <p>HTH!</p> <p>John Saunders, thanks for the correction.</p>
    singulars
    1. This table or related slice is empty.
    1. POI've caught an exception!! Now what?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTodd Sprang
    1. USTodd Sprang
    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. 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
    1. COCareful logging and re-throwing. If you log at each level, you could end up with many, many entries of the same exception in your error log. Google "log rethrow" for a few tips on the right way to go.
      singulars
      1. PO
      1. USWCWedin
    2. CO@JohnSaunders You should consider deleting your comment now that the answer has been fixed.
      singulars
      1. PO
      1. USMark Hurd
    3. CO@Mark: thanks. I didn't know about the change. Downvote removed.
      singulars
      1. PO
      1. USJohn Saunders
 

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