Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You don't have to catch every possible exception around every line of code.</p> <p>Instead, only catch when you have context and you are prepared to handle and take appropriate action. Otherwise, just let it bubble up.</p> <p>Catching exceptions (especially deep in the stack in common functions where you don't have enough context to handle) can be problematic. It sometimes leads to swallowing and not appropriately handling. Handle exceptions when you have context.</p> <p>For that FileInfo exception it depends how deep in that stack it is. If it's in a library where it can be reached via multiple paths and scenarios, you shouldn't handle, what are you going to do at that point? If that's also the case and it bubble all the way out through a deep stack to a GUI performing an operation where you want to handle it, what are you going to catch? Every possible exception of every code path on it's execution path? And, as code changes, you're going to re-evaluate all paths? In a shallow code path (file info dialog that calls that method) it's an easy call but even then you're not going to handle it differently - you're going to display an error dialog or message in panel. Exception types offer the ability to handle <strong>differently</strong>. In both of those case, you handle exception so I say bah hum bug to that guideline. </p> <p><strong>What is very clear is you should not throw type Exception</strong>. That short circuits the ability to handle differently.</p> <p>Another related post:</p> <p><a href="https://stackoverflow.com/questions/7238402/trying-to-understand-exceptions-in-c-sharp/7238519#7238519">Trying to understand exceptions in C#</a></p>
    singulars
    1. This table or related slice is empty.
    1. POCatching exceptions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USbryanmac
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCatching exceptions
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI read that line of thinking a lot, and I don't quite agree with it. Consider two scenarios: (1) System.ArgumentException occurs while trying to open a file at the start of a LoadDocument method, and the effect is that the document doesn't open but system state is otherwise undisturbed; (2) System.ArgumentException occurs at some other point in LoadDocument, as a consequence of e.g. improper cross-thread operation corrupting program state. If the former ArgumentException bubbles up, how can the calling code distinguish it from the latter?
      singulars
      1. PO
      1. USsupercat
    2. COI would suggest that the proper course of action would be to catch and wrap system exceptions in a manner that indicates something about the overall system state. Otherwise, the only way to allow recovery of what should be recoverable exceptions would be to use Pokemon exception handling.
      singulars
      1. PO
      1. USsupercat
 

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