Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can do it this way:</p> <pre><code>case class SocialUser(firstName: String, lastName: String) case class UserDetails(avatarUrl: String, phone: String) case class CombinedUser(user: SocialUser, userDetails: UserDetails) implicit val combinedUserReads: Reads[CombinedUser] = ( (__ \ "user").read(( (__ \ "firstName").read[String] and (__ \ "lastName").read[String] )(SocialUser)) and (__ \ "userDetails").read(( (__ \ "avatarUrl").read[String] and (__ \ "phone").read[String] )(UserDetails)) )(CombinedUser) </code></pre> <p>However its better to create separated <code>Reads</code>:</p> <pre><code>implicit val socialUserReads = ( (__ \ "firstName").read[String] and (__ \ "lastName").read[String] )(SocialUser) implicit val userDetailsReads = ( (__ \ "avatarUrl").read[String] and (__ \ "phone").read[String] )(UserDetails) implicit val combinedUserReads: Reads[CombinedUser] = ( (__ \ "user").read[SocialUser] and (__ \ "userDetails").read[UserDetails] )(CombinedUser) </code></pre> <p>Edit: for simple case classes, <a href="http://www.playframework.com/documentation/2.1.1/ScalaJsonInception">its possible to do</a>:</p> <pre><code>implicit val socialUserReads = Json.format[SocialUser] implicit val userDetailsReads = Json.format[UserDetails] implicit val combinedUserReads = Json.format[CombinedUser] </code></pre> <p><a href="http://www.playframework.com/documentation/2.1.1/ScalaJsonCombinators">Here</a> is quite comprehensive introduction to JSON Reads and more.</p> <blockquote> <p>How about partial objects? If I don't want to fill in every field in the constructor, can I pass empties or do I overload the constructor or similar?</p> </blockquote> <p>Use <code>Option</code>:</p> <pre><code>case class CombinedUser(user: SocialUser, userDetails: Option[UserDetails]) //reads implicit val combinedUserReads: Reads[CombinedUser] = ( (__ \ "user").read[SocialUser] and (__ \ "userDetails").readOpt[UserDetails] )(CombinedUser) //writes implicit val combinedUserWrites: Writes[CombinedUser] = ( //socialUserWrites and userDetailsWrites must be in scope (__ \ "user").write[SocialUser] and (__ \ "userDetails").write[Option[UserDetails]] )(unlift(CombinedUser.unapply)) val json = Json.obj( "user" -&gt; Json.obj( "firstName" -&gt; "Homer", "lastName" -&gt; "Simpson" ) ) Json.fromJson[CombinedUser](json) //JsSuccess(CombinedUser(SocialUser(Homer,Simpson),None),) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POPlay Framework 2.1.1 Json Writes nested objects
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USInfinity
    1. USInfinity
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPlay Framework 2.1.1 Json Writes nested objects
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the answer infinity, its starting to make a bit more sense now. How about partial objects? If I don't want to fill in every field in the constructor, can I pass empties or do I overload the constructor or similar?
      singulars
      1. PO
      1. USmagicaltrout
    2. COThanks infinity, your examples are much more understandable to the newb like me than the docs.
      singulars
      1. PO
      1. USmagicaltrout
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload