StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20335500
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-02T18:44:03.553
FavoriteCount
0
LastActivityDate
2013-12-02T19:05:25.017
LastEditDate
2013-12-02T19:05:25.017
LastEditorUserId
1399502
OwnerUserId
1399502
ParentId
20316224
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Using your example, here is how I might do it using JSON and HAL. A root page: Request: <pre><code>GET / HTTP/1.1 Host: example.com </code></pre> Response: <pre><code>200 OK Content-Type: application/hal+json { "_links": { "self": { "href": "/" }, "students": { "href": "/students" }, "classes": { "href": "/classes" }, "students-with-classes": { "href": "/students?expand" }, } } </code></pre> Creating a new student would be documented on the <code>students</code> relation via posting to the provided href. Presumably I would have previously followed the <code>classes</code> link relation to get the link to class A so that I can include it when adding a user. Request: <pre><code>POST /students HTTP/1.1 Content-Type: application/json { name: "Foo", surname: "Bar", class-link: "/classes/1" } </code></pre> Response: <pre><code>201 Created Location: http://example.com/students/10 </code></pre> Listing the collection of students (following the <code>students-with-classes</code> relation); Request: <pre><code>GET /students?expand HTTP/1.1 </code></pre> Response: <pre><code>200 OK Content-Type: application/hal+json { "_links": { self: { href: "/students" } }, "_embedded": { "students": [ { "_links": { "self": { "href": "/students/1" }, "classes": [ { "href": "/classes/1", "title": "A" } ] }, "name": "Foo1", "surname": "Bar" }, { "_links": { "self": { "href": "/students/2" }, "classes": [ { "href": "/classes/1", "title": "A" } ] }, "name": "Foo2", "surname": "Bar" }, { "_links": { "self": { "href": "/students/3" }, "classes": [ { "href": "/classes/2", "title": "B" } ] }, "name": "Foo3", "surname": "Bar" } ], "classes": [ { "_links": { "self": { "href": "/classes/1" } }, "name": "A", "subject": "Math" }, { "_links": { "self": { "href": "/classes/2" } }, "name": "A", "subject": "Science" } ] } } </code></pre> A couple of things to note: <ul> <li>I <code>POST</code> generic <code>application/json</code> data but retrieve <code>application/hal+json</code>. The representations do not need to be the same in each direction.</li> <li>I use the URI as the resource identifier for the Class to link to, not an artificial external ID. Such an ID may be part of a that URI, but the client should never make that assumption.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POREST how to properly deal with relationships
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJonathan W
UserOwnerUserId
1. USJonathan W
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.