StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20595763
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-15T14:46:02.007
FavoriteCount
0
LastActivityDate
2013-12-15T21:05:10.670
LastEditDate
2013-12-15T21:05:10.670
LastEditorUserId
1831987
OwnerUserId
1831987
ParentId
20595149
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
You almost always want to write your own subclass of AbstractTableModel. At a minimum, you will need to write <code>getRowCount</code>, <code>getColumnCount</code>, and <code>getValueAt</code> methods for it. Typically, a table model returns data based on a private List (such as <code>private List<BoardMessage> messages</code>). The advantage of writing your own model is that the types of each column are a lot easier to keep track of, and there is far less room for error. You can give your model class additional methods like <code>public void addMessage(BoardMessage message)</code> and the model can take care of returning the appropriate values in its getValueAt method. This is much cleaner and less prone to error than just trying to add things to a bare Vector of Vectors. Your model class also acts as, well, a data model, in that you can add a method like <code>public BoardMessage getMessageAt(int row)</code>, which is useful when a user performs an action on a particular message. It's not a good practice to perform JDBC calls inside a table model, because they take time to execute and that will hold up the AWT event dispatch thread, which causes the user interface to become unresponsive. The better thing to do is to execute a JDBC select call in a different Thread, create data objects (such as a List of BoardMessage instances) from the ResultSet, then use <code>EventQueue.invokeLater</code> to update your model with the new data objects.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFormat data from JDBC in JTable with complex TableCellRenderer
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USVGR
UserOwnerUserId
1. USVGR
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.