StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16743687
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-05-24T21:09:19.837
FavoriteCount
0
LastActivityDate
2013-05-24T21:22:38.430
LastEditDate
2013-05-24T21:22:38.430
LastEditorUserId
82548
OwnerUserId
82548
ParentId
16743651
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<p>I'd suggest, though untested:</p> <pre><code>$('tr:not(".headerRow")').first().find('input').change(); </code></pre> <p><a href="http://jsfiddle.net/davidThomas/pSZxG/2/" rel="nofollow">JS Fiddle demo</a>.</p> <p>Further, though, I'd suggest reworking your HTML to take advantage of semantics (Which will simplify your jQuery):</p> <pre><code><table> <thead> <tr class="tblRow headerRow">  </tr> </thead> <tfoot> <tr class="altTblRow totalRow">  </tr> </tfoot> <tbody> <tr class="altTblRow"> <td class="tableCell"> <input type="text" id="input1-1"> </td> <td class="tableCell"> <input type="text" id="input1-2"> </td> <td class="tableCell"> <input type="text" id="input1-3"> </td> </tr>  </tbody> </table> </code></pre> <p>Which would allow you to simply use:</p> <pre><code>$('tbody tr').first().find('input').change(); </code></pre> <p><a href="http://jsfiddle.net/davidThomas/pSZxG/3/" rel="nofollow">JS Fiddle demo</a>.</p> <p>References:</p> <ul> <li><a href="http://api.jquery.com/change/" rel="nofollow"><code>change()</code></a>.</li> <li><a href="http://api.jquery.com/find/" rel="nofollow"><code>find()</code></a>.</li> <li><a href="http://api.jquery.com/first/" rel="nofollow"><code>first()</code></a>.</li> <li><a href="http://api.jquery.com/not-selector/" rel="nofollow"><code>:not()</code> selector</a>.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSelect inputs in first row of table
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDavid Thomas
UserOwnerUserId
1. USDavid Thomas
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSelect inputs in first row of table
  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
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. COI will give this a try. It sounds like a good option.
  singulars
  PostPostId
  PO
  UserUserId
  USPaul Woidke

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.