StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12839209
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-10-11T12:10:04.160
FavoriteCount
0
LastActivityDate
2012-10-11T13:11:38.240
LastEditDate
2012-10-11T13:11:38.240
LastEditorUserId
1066240
OwnerUserId
897024
ParentId
12838661
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
In the <a href="https://github.com/playframework/Play20/wiki/JavaTodoList" rel="nofollow">TodoList example</a>, the site root <code>GET /</code> is mapped to the method <code>Application.index()</code>, so this method creates the html you are seeing. Everything the controller does happens in this line: <code>return ok(index.render("Hello World!"));</code>. Basically it calls some templates which generate html and returns the output. <ul> <li><code>return ok( ... )</code> is used to indicate a successful request, return code 200.</li> <li><code>index.render( ... )</code> returns the rendered html output of a template named <code>index</code>. The package used here is <code>views.html.*</code> but it actually refers to <code>views/index.scala.html</code>. So the <code>index</code> part is no convention, you can rename that part as you like. The template needs to get compiled before it is usable like a Java class, that's why the package names are different. The framework takes care of this.</li> <li><code>"Hello World!"</code> is the argument, as specified as message parameter in the very first line of <code>index.scala.html</code></li> <li><code>@play20.welcome( ... )</code> just calls another template, a <a href="https://github.com/playframework/Play20/blob/master/framework/src/play/src/main/scala/views/play20/welcome.scala.html" rel="nofollow">welcome page</a> which is included in the framework. It's not a subject to change - it's just static page, after removing that line from the view you can put any HTML you want.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUnderstanding the "Welcome to Play 2.0" page creation
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USbiesior
UserOwnerUserId
1. USkapex
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUnderstanding the "Welcome to Play 2.0" page creation
 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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COthank you! :) .. especially for the link to the welcome page on GIT!
 singulars
 PostPostId
 PO
 UserUserId
 USchris

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.