StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16120009
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-04-20T11:50:23.957
FavoriteCount
0
LastActivityDate
2013-04-20T11:50:23.957
LastEditDate
LastEditorUserId
0
OwnerUserId
434223
ParentId
16116586
PostTypeId
2
Score
10
ViewCount
0
LastEditorDisplayName
text
Body
You ask various questions in this single post. I will try to address a few of them. How does a layout work? In Zend Framework 2 there is the concept of "view models". A view model is an object that has a couple of variables and a template assigned. This template is rendered with the given variables. Furthermore, you can nest view models. So one view model (the "layout") has a child which is created from your controller. The child is rendered and stored as a variable in the parent view model. The name of this variable is called the "capture to". What happens, is you have a controller and then a view model is created. This view model is inserted as a child view model in a new model, which is the layout. This child is set with a "capture to" of <code>content</code>. So in the layout, the result of the child view model is inserted in the <code>$content</code> variable. How do you access layout variables in the controller? There is a a <code>layout</code> controller plugin which gives you direct access to the layout view model. So you can set variables directly there: <pre><code>public function indexAction() { $this->layout()->setVariable('foo', 'bar'); } </code></pre> Then <code>$foo</code> echos <code>bar</code> in your layout. How do you access layout variables in a view script? There is a a <code>layout</code> view helper which also gives you direct access to the layout view model. So you can set variables there too: <pre><code><?php $this->layout()->foo = 'bar';?> </code></pre> Then <code>$foo</code> echos <code>bar</code> in your layout.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POZend Framework 2 layout.phtml
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJurian Sluiman
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POZend Framework 2 layout.phtml
 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. COJust what I was looking for :) thanks!
 singulars
 PostPostId
 PO
 UserUserId
 USJoe Walker

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.