Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As a followup to dkatzel's answer, let's assume you start to read from the file in the same try block and the file tells you which value in a array of options to use:</p> <pre><code>String toPrint = {"Hi", "World", "I'm", "A", "String", "Array"}; try{ BufferedReader reader = new BufferedReader( new FileReader("foo.bar") ); String line = reader.readLine(); System.out.println(toPrint[Integer.parseInt(line)]); } catch(Exception e){ println( e.getMessage() ); } </code></pre> <p>Now you have absolutely no idea what really went wrong except through the stack trace. You can't handle any fixable problems. You can't tell in code whether the file doesn't exist (<code>FileNotFoundException</code>), you don't have access to the file, (<code>IOException</code>), if the first line wasn't an Integer (<code>NumberFormatException</code>), or the number was bigger than the array length (<code>ArrayIndexOutOfBoundsException</code>). If you wanted to print a default value if you couldn't read the number, you could instead catch a <code>NumberFormatException</code> and print the value instead of having to quit the entire program.</p> <p>I'll admit this is a pretty contrived example, but it should give you an explanation of why catching <code>Exception</code> is bad. Marko also has a very good answer, stating that it usually is better to let the exception propagate up (especially with <code>RuntimeException</code>s) than to create a bunch of messy code trying to deal with every single problem that can happen.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy use IOexception instead of Exception when catching?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJazzy Josh
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COActually, I think it's a great example. This is why it's so common for people to just use Exception in quick and dirty hacking. It's easy to just parse a stacktrace real quick. However, in a production environment when you want the app to actually try and handle exceptions (so it will keep going instead of crashing and burning), this is exactly why you do NOT want to just snag them all right there.
      singulars
      1. PO
      1. USBrian Knoblauch
    2. CO@BrianKnoblauch It is very rarely meaningful to try to recover from random things which can go wrong. All we do is abort the current unit of work and ensure proper cleanup so that the rest of the application doesn't feel a thing. When exceptions are being caught at all, it is usually when they don't signal problems, but *expected* conditions, such as "no such row in the database".
      singulars
      1. PO
      1. USMarko Topolnik
    3. CO@MarkoTopolnik So are you speaking about [this](http://stackoverflow.com/a/3540710/3080400) methodology? Specifically "checked exceptions lead to bad code and should therefore not be used".
      singulars
      1. PO
      1. USpatterned
 

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