Databases
StackOverflow2013
Postsdbo
POUse case for try-catch-finally with both catch and finally
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUse case for try-catch-finally with both catch and finally
    primarykey
    data
    text
    <p>I understand how <strong>try-catch</strong> works and how <strong>try-finally</strong> works, but I find myself using those (usually) in two completely different scenarios:</p> <ul> <li><strong>try-finally</strong> (or <code>using</code> in C# and VB) is mostly used around some medium-sized code block that uses some resource that needs to be disposed properly.</li> <li><strong>try-catch</strong> is mostly used either <ul> <li>around a single statement that can fail in a very specific way or </li> <li>(as a catch-all) at a very high level of the application, usually directly below some user interface action.</li> </ul></li> </ul> <p>In my experience, cases where a <strong>try-catch-finally</strong> would be appropriate, i.e., where the block in which I want to catch some particular exception is <em>exactly</em> the same block in which I use some disposable resource, are extremely rare. Yet, the language designers of <a href="http://msdn.microsoft.com/en-us/library/dszsf989.aspx" rel="noreferrer">C#</a>, <a href="http://msdn.microsoft.com/en-us/library/fk6t46tz.aspx" rel="noreferrer">VB</a> and <a href="http://java.sun.com/docs/books/tutorial/essential/exceptions/putItTogether.html" rel="noreferrer">Java</a> seem to consider this to be a highly common scenario; the VB designers <a href="http://blogs.msdn.com/lucian/archive/2010/02/15/req13-catches-in-using-blocks.aspx" rel="noreferrer">even think about adding <strong>catch</strong> to <code>using</code></a>.</p> <p>Am I missing something? Or am I just overly pedantic with my restrictive use of <strong>try-catch</strong>?</p> <hr> <p>EDIT: To clarify: My code usually looks like this (functions unrolled for clarity):</p> <pre><code>Try do something Aquire Resource (e.g. get DB connection) Try do something Try do something that can fail Catch SomeException handle expected error do something else... Finally Close Resource (e.g. close DB connection) do something Catch all handle unexpected errors </code></pre> <p>which just seems to make much more sense than putting any of the two catches on the same level as <em>finally</em> just to avoid indentation.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USHeinzi
    1. USHeinzi
    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. POUse case for try-catch-finally with both catch and finally
      1. USJørn Schou-Rode
      1. VTFavorite
    2. VO
      singulars
      1. POUse case for try-catch-finally with both catch and finally
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUse case for try-catch-finally with both catch and finally
      1. This table or related slice is empty.
      1. VTUpMod
    1. COwhere did you get the feeling that the language designers consider it a highly common scenario? It's just documentation so they try to write in a general way; thus always using try-catch-finally in examples
      singulars
      1. POUse case for try-catch-finally with both catch and finally
      1. USThanos Papathanasiou
    2. CONot all languages do it this way. F# only allows either equivalents to try-catch or try-finally but not try-catch-finally.
      singulars
      1. POUse case for try-catch-finally with both catch and finally
      1. USkvb
    3. CODoes your "Catch All" block release the resource? If yes, you have it in two places (see the first "finally") if not, you risk resource leaks.
      singulars
      1. POUse case for try-catch-finally with both catch and finally
      1. USp.marino
 

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