StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
394897
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-12-27T11:05:09.193
FavoriteCount
0
LastActivityDate
2008-12-27T11:05:09.193
LastEditDate
LastEditorUserId
0
OwnerUserId
22682
ParentId
394504
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Another smart extension to what you are doing, is not to do the ajax call as soon as a key is pressed. If the user types in a long word quickly, you'll get multiple ajax http requests triggered faster than they can return and update your UI. This adds to your server load, and might make the client's UI sluggish. Instead, onkeypress, store all the appropriate details and then call var timeout = setTimeout('some_method()',100); Which says call the some_method() in 100 milliseconds. The first thing you should do within your keypress method is cancel/clear the Timeout call with clearTimeout. <a href="http://www.w3schools.com/js/js_timing.asp" rel="nofollow noreferrer">http://www.w3schools.com/js/js_timing.asp</a> The some_method() should also clear any timeout, then make the http ajax request. The net effect here is that your ajax request is delayed slightly, but never happens if the user presses another key. Or put another way, don't try and fire an ajx request until the user has stopped/paused typing. 100 milliseconds might be too high or too low, but you hopefully get the idea! You should also take care to deal with a "slow server" situation. Consider this: <ul> <li>User types "hello", pauses for 1 second, you fire an ajax request with "hello" as the parameter</li> <li>User continues to type " world", so the textfield now contains "hello world", and stops typing.</li> <li>You fire a second ajax request with "hello world" as the parameter.</li> <li>The second request (for "hello world") returns first, you update your UI</li> <li>The first request (for "hello") returns, you update your UI again.</li> </ul> Ooops! Have the server include the original query string in the (json) data it returns to the client. When the client gets the ajax data back, check that the result/data is for the query ("hello" / "hello world") that matches what is currently in the text field.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POjQuery .load seems to be running at an unexpected point
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmintywalker
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
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.