StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8355722
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-12-02T11:34:29.990
FavoriteCount
0
LastActivityDate
2011-12-02T11:53:46.150
LastEditDate
2011-12-02T11:53:46.150
LastEditorUserId
139985
OwnerUserId
139985
ParentId
8355668
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
An exception could be caught at that point if <pre><code>Object o = (Object)iter.next(); </code></pre> or <pre><code>System.out.println(o.hashCode()); </code></pre> throw an unchecked exception. Here are a couple of possibilities: <ul> <li>If you had previously called <code>addObject(null)</code>, a call to <code>update()</code> would lead to a NullPointerException when it calls <code>hashCode()</code> on a <code>null</code> reference. </li> <li>If you have an instance of <code>Foo</code> shared by two threads, and one calls <code>addObject</code> while the other is calling <code>compute()</code>, then you could get a <code>ConcurrentModificationException</code>.</li> <li>If <code>Vector</code> was a custom class and not <code>java.util.Vector</code>, then <code>iter.next()</code> could throw some other unchecked exception ... at the whim of the author of said custom class. (OK ... unlikely in the light of the OP's comments.)</li> <li>(From aix's answer) - <code>o.hashCode()</code> could in theory throw any unchecked exception, depending on how <code>o</code>'s class implements the <code>hashCode()</code> method.</li> <li>There may be other possibilities too.</li> </ul> <hr> If you are merely curious as to what the possible exceptions might be, the above more or less covers it. If you want to tidy up this code, then it is probably a bad thing to be catching <code>Exception</code> at that point. Each of those cases listed is a sign of a bug here or elsewhere in the application. Rather that catching the exception at that point and (presumably) trying to "make good" the problem, it is better to bomb out with a stacktrace, and then go back and fix the root problem that was being hidden by the catch.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POExceptions in java with vectors and iterators
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USStephen C
UserOwnerUserId
1. USStephen C
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POExceptions in java with vectors and iterators
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COThanks. Point Taken.
 singulars
 PostPostId
 PO
 UserUserId
 USn3o

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.