StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10527400
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-05-10T04:12:16.217
FavoriteCount
0
LastActivityDate
2012-05-10T04:12:16.217
LastEditDate
LastEditorUserId
0
OwnerUserId
1152959
ParentId
9739613
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
View caching, by nature, doesn't actually execute the controller's method on every request. I'm guessing it executes the action once and then caches the output to disk (or, whatever cache engine you happen to be using). If you <a href="http://api20.cakephp.org/view_source/cache-helper#l-262" rel="nofollow">look at the CacheHelper's <code>_writeFile</code> method</a>, you can see how the cached view is constructed. <pre class="lang-php prettyprint-override"><code> $file = '<?php'; if (empty($this->_View->plugin)) { $file .= " App::uses('{$this->_View->name}Controller', 'Controller'); "; } else { $file .= " App::uses('{$this->_View->plugin}AppController', '{$this->_View->plugin}.Controller'); App::uses('{$this->_View->name}Controller', '{$this->_View->plugin}.Controller'); "; } $file .= ' $request = unserialize(\'' . str_replace("'", "\\'", serialize($this->request)) . '\'); $response = new CakeResponse(array("charset" => Configure::read("App.encoding"))); $controller = new ' . $this->_View->name . 'Controller($request, $response); $controller->plugin = $this->plugin = \'' . $this->_View->plugin . '\'; $controller->helpers = $this->helpers = unserialize(base64_decode(\'' . base64_encode(serialize($this->_View->helpers)) . '\')); $controller->layout = $this->layout = \'' . $this->_View->layout . '\'; $controller->theme = $this->theme = \'' . $this->_View->theme . '\'; $controller->viewVars = unserialize(base64_decode(\'' . base64_encode(serialize($this->_View->viewVars)) . '\')); Router::setRequestInfo($controller->request); $this->request = $request;'; if ($useCallbacks == true) { $file .= ' $controller->constructClasses(); $controller->startupProcess();'; } $file .= ' $this->viewVars = $controller->viewVars; $this->loadHelpers(); extract($this->viewVars, EXTR_SKIP); ?>'; </code></pre> It creates a new <code>Controller</code> object (with a new CakeResponse) and loads all the helpers, plugins, etc that may be used in the view and writes it to cache. It appears that adding the <code>Last-Modified</code> header to the response of a cache action/view might require some deep modifications to the core CakePHP library.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCakePHP 2.1: Browser cache vs View cache
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USsesser
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCakePHP 2.1: Browser cache vs View cache
 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
 VTAcceptedByOriginator
CommentsPostId
1. COYes, any modification to the Response object made by a Controller action will not be cached, this includes the setting of Cache control headers. There is an open ticket about this (although not Caching related): http://cakephp.lighthouseapp.com/projects/42648/tickets/2358-cachehelper-defect-with-response The only suggested workaround is setting headers manually in either the layout or `Controller::beforeFilter()` (with callback enabled).
 singulars
 PostPostId
 PO
 UserUserId
 USpixelistik

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.