Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here you've chanced on one of the biggest religious schisms in the Java, ( if not wider ) , world. It boils down to those that feel, as TJ seems to, and I do too, that checked exceptions are valuable for many reasons, VS the Rod Johnson/Spring school that in the design of Java, checked exceptions were used in many instances where they shouldn't, say closing a resultset or socket, so because it was wrongly used in many cases, it makes them useless so all exceptions should be unchecked. There are many classes in the Spring framework that are very thin wrappers around standard Java objects, but convert checked exceptions to unchecked. It drives me berserk! </p> <p>Anyway, put me down as strongly agreeing with everything TJ has said, but know that you'll probably never find a "right" answer.</p>
    singulars
    1. This table or related slice is empty.
    1. PORethrowing checked exceptions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmezmo
    1. USmezmo
    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. This table or related slice is empty.
    1. COThe main "problem" with Java's checked exceptions is the lack of a concise syntax to indicate that a called method isn't expected to throw certain (or any) exceptions. If even 25% of a method's callers would be interested in catching a particular exception, having it as a checked exception would be semantically advantageous, but for the fact that it would force a few lines of code bloat on each of the 75% of callers that weren't interested in it. As it is, checked exceptions are more of a hindrance than a help unless 90%+ of callers will be interested.
      singulars
      1. PO
      1. USsupercat
    2. COI do agree with what you're saying, but I've also had to take over code that was written with Spring and unchecked exceptions, where the original author felt it necessary to implement a lot of his business logic in unchecked exceptions, years later we're STILL finding small libraries that were used throwing exceptions we had no idea might be tripped across.
      singulars
      1. PO
      1. USmezmo
    3. COThe problem there I think is that there isn't with checked exceptions or a lack thereof, but rather with an exception hierarchy that doesn't distinguish between "Method failed with no side-effects; object appears undamaged" and "CPU is on fire". Any exception thrown by `myDocument = SomeDocumentClass.LoadDocument(filename);` will, at minimum, have the effect that `myDocument` won't get loaded; if the caller can deal with that, it should consider itself prepared to handle all exceptions where that is the only effect/implication, whether or not it anticipated the *particular* reason for failure.
      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