StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20115656
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-11-21T08:17:59.707
FavoriteCount
0
LastActivityDate
2013-11-21T08:17:59.707
LastEditDate
LastEditorUserId
0
OwnerUserId
226975
ParentId
20114532
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You can use HTTP's <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.1.3" rel="nofollow">cache-control mechanisms</a> to control the browser's caching. When serving a copy of your JS file, include an <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.19" rel="nofollow">ETag</a> and/or <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.29" rel="nofollow">Last-Modified</a> header in the response. Also include a "<a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9" rel="nofollow">Cache-Control</a>: must-revalidate" header. This tells the browser that it must check back with the server every time, and it can send an <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.26" rel="nofollow">If-None-Match</a> and/or <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.25" rel="nofollow">If-Modified-Since</a> header in future requests to ask the server to send the file only if it's changed. If you'd like to avoid the load of browsers checking with the server every time, and it's OK for the changes to not take effect immediately, you can also include a <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.18" rel="nofollow">Date</a> header with the current time and an <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.21" rel="nofollow">Expires</a> header set to some point in the future — maybe 12 or 24 hours. That allows the browser to use its cached copy for the specified amount of time before it has to check back with your server again. HTTP's cache-control features are pretty robust, but there are plenty of nuances, such as controls for intermediate caches (e.g. other systems between your server and the user's browser). You'll want to read about <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13" rel="nofollow">caching in HTTP</a> overall, not just the specific header fields that I've mentioned.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to force refresh client js from server side?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USWyzard
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to force refresh client js from server side?
 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. COthank you very much.
 singulars
 PostPostId
 PO
 UserUserId
 USAllerson

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.