Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Normally I use something like this to try and catch all unexpected top-level exceptions.</p> <pre><code>using System; static class Program { [STAThread] static void Main(string[] argv) { try { AppDomain.CurrentDomain.UnhandledException += (sender,e) =&gt; FatalExceptionObject(e.ExceptionObject); Application.ThreadException += (sender,e) =&gt; FatalExceptionHandler.Handle(e.Exception); // whatever you need/want here Application.Run(new MainWindow()); } catch (Exception huh) { FatalExceptionHandler.Handle(huh); } } static void FatalExceptionObject(object exceptionObject) { var huh = exceptionObject as Exception; if (huh == null) { huh = new NotSupportedException( "Unhandled exception doesn't derive from System.Exception: " + exceptionObject.ToString() ); } FatalExceptionHandler.Handle(huh); } } </code></pre> <p>Maybe it is something you find helpful too? This main code routes all three ways of catching unexpected top-level exceptions through one method call. All you now need is a static class <code>FatalExceptionHandler</code> that includes your top-level exception handling in its <code>Handle</code> method.</p> <p>And really, any application developer knows there are really just two things to do there:</p> <ol> <li>Show/log the exception like you see fit</li> <li>Make sure you exit/kill the application process</li> </ol> <p>If you think item two is strange, remember that we only bother to do this in the first place for really exceptional situations. These things are probably bugs that need changes to your application to be accurately addressed. Any other exception handling - the functional kind - should be lower down inside your actual program code, catching specific kinds of exceptions where this makes sense and handling them there in the way that makes sense. Anything else should bubble up to your <code>FatalExceptionHandler</code> to make itself known and stop the possibly crippled program from working from corrupted state</p> <p>Dead programs tell no lies... ;-)</p>
    singulars
    1. This table or related slice is empty.
    1. POHandling unhandled exceptions problem
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USpeSHIr
    1. USpeSHIr
    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. VTDownMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 for Dead programs tell no lies... ;-)
      singulars
      1. PO
      1. USMunish Goyal
    2. COAs you can see from this [Why is UnhandledExceptionEventArgs.ExceptionObject an object and not an Exception?](http://stackoverflow.com/questions/913472/why-is-unhandledexceptioneventargs-exceptionobject-an-object-and-not-an-exception) post, it *may* be unwise to cast `e.ExceptionObject` to `Exception` without a check first, as it will not always be of type `Exception`... you could end up creating a new `Exception` here.
      singulars
      1. PO
      1. USSheridan
    3. COWondered why it was object, but never actually looked into this. I learned something new today. Thanks! Will change answer to try and remedy this.
      singulars
      1. PO
      1. USpeSHIr
 

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