Grails

• Type: Sub-task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.2
• Fix Version/s: 1.1-beta3
• Component/s: Persistence
• Labels:

  None

If I have the following two classes:

class Employee {
static hasMany = [projects: Project]
static mapping = { projects joinTable: [name: 'EMP_PROJ', column: 'PROJECT_ID', key: 'EMPLOYEE_ID'] }
}

class Project {
static belongsTo = Employee
}

I expect three tables (EMPLOYEE, PROJECT, EMP_PROJ), but instead of EMP_PROJ I get EMPLOYEE_PROJECT. It ignores the joinTable:name parameter (but not the column or key parameters). The reason is the belongsTo clause in Project. If I remove the belongsTo then I get EMP_PROJ as I wanted, but now Employee.delete() doesn't cascade to the related Projects. The workaround is to explicitly define the cascade behavior using something like:

projects joinTable: [name: 'EMP_PROJ', column: 'PROJECT_ID', key: 'EMPLOYEE_ID'], cascade: 'all,delete-orphan'

• Assignee:

  Graeme Rocher

  Reporter:

  Tyler Williams

• Created:

  30/May/08 5:23 PM

  Updated:

  18/May/11 3:16 PM

  Resolved:

  21/Jan/09 9:03 AM