{"id":17109,"date":"2015-02-06T15:07:44","date_gmt":"2015-02-06T09:37:44","guid":{"rendered":"https:\/\/2thenew.today\/blog\/?p=17109"},"modified":"2015-07-24T16:59:56","modified_gmt":"2015-07-24T11:29:56","slug":"significance-of-mappedby-in-grails-domain","status":"publish","type":"post","link":"https:\/\/2thenew.today\/blog\/significance-of-mappedby-in-grails-domain\/","title":{"rendered":"Significance of \u201cmappedBy\u201d in Grails Domain"},"content":{"rendered":"

“mappedBy” is a static map which is used to determine and change the way two associated domain classes interact with each other.<\/p>\n

Let’s start with the role of “mappedBy”\u00a0in one-to-many relationships.<\/p>\n

Consider the following Example:-<\/p>\n

[code]class Team {
\n\u2003\u2003\u2003\u2003static hasMany = [members: TeamMember]
\n}[\/code]<\/p>\n

 <\/p>\n

[code]class TeamMember {
\n\u2003\u2003\u2003\u2003Team memberOf
\n\u2003\u2003\u2003\u2003Team captainOf
\n}[\/code]<\/p>\n

The Team domain contains a one-to-many association (members) with TeamMember domain which has multiple properties (memberOf, captainOf) of Team type. This makes the association bi-directional.<\/p>\n

Now, Grails\u00a0won’t know which<\/a> of the properties (memberOf or captainOf) of TeamMember domain it needs to involve while creating this bi-directional one-to-many association and it will give the following error:<\/p>\n

\"Property [members] in class [class Team] is a bidirectional one-to-many \r\nwith two possible properties on the inverse side. Either name one of the properties on \r\nother side of the relationship [team] or use the 'mappedBy' static to define the property \r\nthat the relationship is mapped with. Example: static mappedBy = [members:'myprop']\"<\/pre>\n
To resolve this, we declare “mappedBy” on the \u201cone\u201d side of this association:<\/p>\n
[code]class Team {
\n\u2003\u2003\u2003\u2003static hasMany = [members: TeamMember]
\n\u2003\u2003\u2003\u2003static mappedBy = [members: ‘memberOf’]
\n}[\/code]<\/p>\n
This way Grails would know that [members]<\/strong> of Team<\/strong> has a bi-directional one-to-many association with [memberOf]<\/strong> of TeamMember<\/strong> and it will infer that Team<\/strong> is associated with TeamMember<\/strong> in a one-to-one relationship using the property [captainOf]<\/strong>.<\/p>\n
\n
On that note, lets consider the case of many-to-many relationships.<\/p>\n
Here’s an example :-<\/p>\n
[code]class User {
\n\u2003\u2003\u2003\u2003static hasMany = [writtenPosts: Article, subscribedPosts: Article]
\n}[\/code]<\/p>\n
[code]class Article {
\n\u2003\u2003\u2003\u2003User writer
\n\u2003\u2003\u2003\u2003static hasMany = [subscribers: User]
\n\u2003\u2003\u2003\u2003static belongsTo = [User]
\n}[\/code]<\/p>\n
These domains are associated with each other in 2 ways:<\/p>\n
    \n
  1. [writtenPosts]<\/strong> of User<\/strong> is associatemany-to-one relationship.d with [writer]<\/strong> of Article<\/strong> in a bi-directional<\/li>\n
  2. [subscribedPosts]<\/strong> of User<\/strong> is associated with [subscribers]<\/strong> of Article<\/strong> in a many-to-many relationship.<\/li>\n<\/ol>\n
    With this code, Grails will create 4 tables for these 2 classes:<\/p>\n
    1. user(id, version, name)\r\n2. article(id, version, description, writer_id)\r\n3. user_subscribed_posts(user_id, article_id)\r\n4. user_written_posts(user_id, article_id)\r\n<\/pre>\n
    The 4th table is redundant as the same information would be stored in [writer_id]<\/strong> column of article<\/strong> table. To prevent this, we declare \u201cmappedBy\u201d in the User<\/strong> domain specifying:<\/p>\n
      \n
    1. [writtenPosts]<\/strong> of User<\/strong> is associated with [writer]<\/strong> of [Article]<\/strong>.<\/li>\n
    2. [subscribedPosts]<\/strong> of User<\/strong> is associated with [subscribers]<\/strong> of Article<\/strong>.<\/li>\n<\/ol>\n
       <\/p>\n
      [code]class User {
      \n\u2003\u2003\u2003\u2003static hasMany = [writtenPosts: Article, subscribedPosts: Article]
      \n\u2003\u2003\u2003\u2003static mappedBy = [writtenPosts: ‘writer’, subscribedPosts: ‘subscribers’]
      \n}[\/code]<\/p>\n
      Now, when this code runs only 3 tables are created:<\/p>\n
      1. user(id, version, name)\r\n2. article(id, version, description, writer_id)\r\n3. user_subscribed_posts(user_id, article_id)\r\n<\/pre>\n
      By using “mappedBy” we can direct Grails towards the correct relationship or change the inferred relationship between multiple domains to suite our needs.<\/p>\n
      I came by this topic while perusing through Grails\u00a0wiki<\/a> and thought of sharing this with everyone.<\/p>\n
      Hope you enjoyed reading this blog.<\/p>\n","protected":false},"excerpt":{"rendered":"
      “mappedBy” is a static map which is used to determine and change the way two associated domain classes interact with each other. Let’s start with the role of “mappedBy”\u00a0in one-to-many relationships. Consider the following Example:- [code]class Team { \u2003\u2003\u2003\u2003static hasMany = [members: TeamMember] }[\/code]   [code]class TeamMember { \u2003\u2003\u2003\u2003Team memberOf \u2003\u2003\u2003\u2003Team captainOf }[\/code] The Team […]<\/p>\n","protected":false},"author":159,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":73,"footnotes":""},"categories":[7],"tags":[4840,1630,1627,1629],"class_list":["post-17109","post","type-post","status-publish","format-standard","hentry","category-grails","tag-grails","tag-many-to-many","tag-mappedby","tag-one-to-many"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t