StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19551236
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-10-23T20:03:07.460
FavoriteCount
0
LastActivityDate
2013-10-23T20:18:03.003
LastEditDate
2013-10-23T20:18:03.003
LastEditorUserId
1274818
OwnerUserId
1274818
ParentId
17596809
PostTypeId
2
Score
15
ViewCount
0
LastEditorDisplayName
text
Body
Play has a lot of new features for JSON right now. This would be a nice showcase for the <code>Format[A]</code> trait (see <a href="http://www.playframework.com/documentation/2.1.x/ScalaJsonInception">Scala Json Inception</a>) which you could include implicitly as I will show, or explicitly to the methods that require an implicit <code>Format[A]/Reads[A]/Writes[A]</code>. Create a case class to represent your JSON objects, <pre><code>case class Book(id: Int, name: String) case class BookDetail(id: Int, author: String, publicationDate: Int, pages: Int) </code></pre> Create companion objects that contain the implicit <code>Format[A]</code> so that <code>Format/Reads/Writes</code> will automatically be in scope when you need them. <pre><code>object Book { implicit val fmt: Format[Book] = Json.format[Book] } object BookDetail { implicit val fmt: Format[BookDetail] = Json.format[BookDetail] } </code></pre> Now you could do something like this, <pre><code>val bookJson = Json.toJson(Book(1, "A Brief History Of Time")) val bookDetailJson = Json.toJson(BookDetail(1, "Steven Hawking", 1988, 256)) bookJson.as[JsObject].deepMerge(bookDetailJson.as[JsObject]) </code></pre> And you will have an object like this, <pre><code>{ id: 1, name: "A Brief History Of Time", author: "Steven Hawking", publicationDate: 1988, pages: 256 } </code></pre> I've tried this in the REPL but it does not work, in a Play application it does just fine though. Also in a production scenario we would likely use <code>asOpt[T]</code> in place of <code>as[T]</code>. Here is an example of why <code>asOpt[T]</code> may be better suited, suppose instead of a valid JSON object for book you get, <pre><code>val bookJson = Json.toJson("not a book") </code></pre> You will end up with a <pre><code>[JsResultException: JsResultException(errors:List((,List(ValidationError(validate.error.expected.jsobject,WrappedArray())))))] </code></pre> But suppose instead you change your method to use <code>asOpt[T]</code>, <pre><code>bookJson.asOpt[JsObject].getOrElse(Json.obj()).deepMerge(bookDetailJson.asOpt[JsObject].getOrElse(Json.obj())) </code></pre> Now you will end up with at least a partial JSON object, <pre><code>{ id: 1, author: "Steven Hawking", publicationDate: 1988, pages: 256 } </code></pre> So depending on how you would like to handle improperly formatted JSON you could choose either option.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to merge a JsValue to JsObject in flat level
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UStysonjh
UserOwnerUserId
1. UStysonjh
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.