StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
156603
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-10-01T07:46:25.947
FavoriteCount
0
LastActivityDate
2008-10-01T08:56:26.590
LastEditDate
2008-10-01T08:56:26.590
LastEditorUserId
11438
OwnerUserId
11438
ParentId
156552
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
joelhardi
text
Body
I second Ken's rec of PEAR's <a href="http://pear.php.net/package/Cache_Lite" rel="noreferrer">Cache_Lite</a> library, you can use it to easily cache either parts of pages or entire pages. If you're running your own server(s), I'd strongly recommend <a href="http://www.danga.com/memcached/" rel="noreferrer">memcached</a> instead. It's much faster since it runs entirely in memory and is used extensively by a lot of high-volume sites. It's a very easy, stable, trouble-free daemon to run. In terms of your PHP code, you'd use it much the same way as Cache_Lite, to cache various page sections or full pages (or other arbitrary blobs of data), and it's very easy to use since PHP has a <a href="http://www.php.net/manual/en/intro.memcache.php" rel="noreferrer">memcache interface built in</a>. For super high-traffic full-page caching, take a look at doing <a href="http://varnish.projects.linpro.no/" rel="noreferrer">Varnish</a> or <a href="http://www.squid-cache.org/" rel="noreferrer">Squid</a> as a caching reverse proxy server. (Pages that get served by Varnish are going to come out easily 100x faster than anything that hits the PHP interpreter.) Keep in mind with caching, you really only need to cache things that are being frequently accessed. Sometimes it can be a trap to develop a really sophisticated caching strategy when you don't really need it. For a page like your home page that's getting hit several times a second, you definitely want to optimize it for speed; for a page that gets maybe a few hits an hour, like a month-old blog post, it's a bad idea to cache it, you only waste your time and make things more complicated and bug-prone.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCreating a two-pass PHP cache system with mutable items
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USjoelhardi
UserOwnerUserId
1. USjoelhardi
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCreating a two-pass PHP cache system with mutable items
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. 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.