Grails one to one on two domain object

Question

I want to add a child to two different parent class, like that:

First:

class Member {
    Profile profile

    Member() {
        this.profile = new Profile()
    }

    static mapping = {
        profile cascade: 'all-delete-orphan'
    }
}

Second:

class Team {
    Profile profile

    Team() {
        this.profile = new Profile()
    }

    static mapping = {
        profile cascade: 'all-delete-orphan'
    }
}

Thw child is simply define like that

  class Profile() {
  }

The probleme is when I save the parent, it dosent save the child:

Member member = new Member().save(flush: true, failOnError: true)

assert !member.hasErrors()
assert member.profile           
assert !member.profile.hasErrors()

assert member.profile.id //FAIL

What do I do wrong? Is there a better way to do it?

UPDATE:

I found this

Saving associated domain classes in Grails

It seem that 'belong to' is needed for that kind of behavior. But Why the 'cascade: 'all-delete-orphan' doesn't force this ? Because I can't use 'belong to' in that specific case

Sorry, I made a mistake typing my question. It's corrected now, thanks to have pointed it! — Thermech, May 09 '13 at 09:52
Yeah, it seam to have a probleme with the session.flush while in a unit test. — Thermech, May 10 '13 at 14:24

score 0 · Answer 1 · answered May 09 '13 at 14:21

I copied your example (with slight modification to change group table name to a non-reserved word) and the cascades are working properly using grails 2.2.1. Both Member and Group cascaded their saves to the newly created Profiles.

Assuming your classes are more complicated than this, you might have an error elsewhere in your class (eg cascade behavior described in constraints instead of mapping, etc).

Thermech · Accepted Answer · 2013-05-28T13:04:28.707

0

I found a nice solution. The best was to define both parent in the child but nullable. Like that:

class Profile() {
    static belongsTo = [member: Member, team: Team]

    static constraints = {
        member nullable: true
        team nullable: true
    }
}

This way, the cascade behavior work just fine !

edited May 28 '13 at 13:04

answered May 10 '13 at 17:10

Thermech

4,371
2
39
60

Grails one to one on two domain object

2 Answers2