grails deleted对象将通过级联错误重新保存

Der*_*rek 6 grails hibernate grails-orm

我将项目设置如下.我想删除一个项目,我得到以下内容:

2010-09-29 11:45:22,902 [http-8080-1] ERROR errors.GrailsExceptionResolver  - deleted object would be re-saved by cascade (remove deleted object from associatio
ns): [Project#204]
org.hibernate.ObjectDeletedException: deleted object would be re-saved by cascade (remove deleted object from associations): [Project#204]
        at ProjectController$_closure6.doCall(ProjectController:50)
        at ProjectController$_closure6.doCall(ProjectController)
        at org.jsecurity.web.servlet.JSecurityFilter.doFilterInternal(JSecurityFilter.java:382)
        at org.jsecurity.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:180)
        at java.lang.Thread.run(Thread.java:619)
Run Code Online (Sandbox Code Playgroud)

有没有办法让hibernate告诉我哪个对象有引用回到将被重新保存的Project对象.我的项目设置导致此循环异常有什么问题?

public class Project implements Comparable
{  
    static belongsTo = [employee:Employee]

    static hasMany = [roles:Role]
    static constraints = {

    }
    static mapping = {
          description type:"text"
          roles lazy:false, cascade:"all,delete-orphan"
          client lazy:false, cascade:"all,delete-orphan"
          employer lazy:false, cascade:"all,delete-orphan"
    }
}


class Employee implements Comparable
{
    static hasMany = [employeeDesiredSkills:EmployeeDesiredSkill,
                      employeeDesiredTools:EmployeeDesiredTool,
                      employeeAreasOfExpertise:EmployeeAreaOfExpertise,
                      projects:Project,
                      education:Education]


    static mapping = {
           employeeDesiredSkills cascade:"all,delete-orphan", lazy:false
           employeeDesiredTools cascade:"all,delete-orphan", lazy:false
           education cascade:"all,delete-orphan", lazy:false
           projects cascade:"all,delete-orphan", lazy:false
    }
}

public class Role implements Comparable
{

    static belongsTo = [project:Project]
    static hasMany = [roleSkills:RoleSkill,roleTools:RoleTool]

    static mapping = {
        duties type:"text"
        roleSkills cascade:"all,delete-orphan", lazy:false
        roleTools cascade:"all,delete-orphan", lazy:false
        locationType cascade:"all,delete-orphan", lazy:false

    }

    static contraints = {
        endDate(nullable: true)
        roleSkills(nullable: true)
        roleTools(nullable: true)
    }
}

class Employer implements Comparable
{
   static mapping = {
       type lazy:false, cascade:"all,delete-orphan"
   }
}

class RoleTool implements Comparable    
{


  static belongsTo = [role:Role, tool:Tool]//not sure this makes sense, but have to leave it or DB breaks
  Tool tool = new Tool(name:"")
    static mapping = {
      tool cascade:"save-update", lazy:false

    }


class RoleSkill implements Comparable   
{

  static belongsTo = [role:Role, skill:Skill]//not sure this makes sense, but have to leave it or DB breaks
    Skill skill = new Skill(name:"")
    static mapping = {
       skill cascade:"save-update", lazy:false

    }
}

class Skill implements Comparable
{
    static hasMany = [roleSkills:RoleSkill, employeeDesiredSkills:EmployeeDesiredSkill]

    static mapping = {
        roleSkills cascade:"all,delete-orphan", lazy:false
        employeeDesiredSkills cascade:"all,delete-orphan", lazy:false

    }

}

class Tool implements Comparable
{

    static hasMany = [roleTools:RoleTool, employeeDesiredTools:EmployeeDesiredTool]

    static mapping = {
        roleTools cascade:"all,delete-orphan", lazy:false
        employeeDesiredTools cascade:"all,delete-orphan", lazy:false

    }
}
Run Code Online (Sandbox Code Playgroud)

Him*_*shu 9

事实上,您projects cascade:"all,delete-orphan" 在Employee类中完成映射的方式 .

你只需要这样做:

def employee = project.employee; 
employee.removeFromProjects(project);
Run Code Online (Sandbox Code Playgroud)

该项目也将被删除.有关更多详细信息,请参阅Peter Ledbrook的GORM Gotchas.它是一个3部分系列,并解释了许多类似的情况

  • 我终于搞定了.事实并非那么简单.我认为如果项目存储在SortedSet中有一个grails错误,那么它很难做到删除.我不得不复制项目,删除我想要删除的项目,然后将它们添加回员工以使其工作 (2认同)

Ale*_*ier 5

我知道它已经晚了但是有人可能想在这里找到这个:发生了什么是Hibernate使用'dirtyChecking',正如GORM Gotchas By Peter Ledbrook所解释的那样.

为了使事情短:休眠,所以Grails将要save()employee在Hibernate会话结束时(在你的情况的对象.delete(flush:true)调用),因为它检测到物体已经被修改(一个project已被抑制).而且employee必须不停地被一个链接project,导致Hibernate来会觉得你delete()projectsave()它回来了.

要解决此问题:

 def employee = project.employee; 
 employee.discard(); 
 project.delete(flush:true);
Run Code Online (Sandbox Code Playgroud)

这告诉不休眠到save()employee没有你自讨苦吃.