Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A <code>RuntimeException</code> should be used only when the client cannot recover from whatever the problem is. It is occasionally appropriate to do what you are talking about, but more often it is not appropriate.</p> <p>If you are using a JDK >= 1.4, then you can do something like:</p> <pre> try { // Code that might throw an exception } catch (IOException e) { throw new RuntimeException(e); } catch (ClassNotFoundException e) { throw new RuntimeException(e); } </pre> <p>and the rethrown <code>RuntimeException</code> will have the original cause included inside it. This way, someone at the top of the thread catching the <code>RuntimeException</code> -- your threads do catch <code>RuntimeException</code> so they don't just silently die, right? -- can at least print out the FULL stack trace of the cause.</p> <p>But as others have said and will say, exceptions are checked for a reason. Only do this when you are positive that your clients cannot recover from the problem that you are rethrowing as an unchecked exception.</p> <p>NOTE: Better than just <code>RuntimeException</code> would be to use a more specific unchecked exception if one is available. For example, if the only reason your method could throw a <code>ClassNotFoundException</code> is because a configuration file is missing, you could rethrow a <code>MissingResourceException</code>, which is an unchecked exception but gives more information about why you are throwing it. Other good <code>RuntimeException</code>s to use if they describe the problem you are rethrowing are <code>IllegalStateException</code>, <code>TypeNotPresentException</code> and <code>UnsupportedOperationException</code>.</p> <p>Also note that it is ALWAYS a good idea for your threads to catch RuntimeException and at a minimum log it. At least this way you understand why your threads are going away.</p>
    singulars
    1. This table or related slice is empty.
    1. POWrapping a checked exception into an unchecked exception in Java?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USEddie
    1. USEddie
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWrapping a checked exception into an unchecked exception in Java?
      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. COEven better, extends RuntimeException.
      singulars
      1. PO
      1. USLoki
    2. COI prefer to keep my exceptions generic and stay away from custom ones, where possible.
      singulars
      1. PO
      1. USJames McMahon
    3. COIt's OK to stay away from custom exceptions, which is why I mentioned several of the most useful RuntimeExceptions that already exist as part of Java. A more specific Exception really helps during debugging.
      singulars
      1. PO
      1. USEddie
 

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