更新拦截器上的父亲
我的模型：
public class Father {
Set<Son> sons = new HashSet<Son>();
String name = null;
Date lastSonModifyDate = null;
// ... other fields and setters/getters
}
public class Son {
Father father = null;
String name = null;
Date lastModifyDate = null;
// ... other fields and setters/getters
}
用例：
- 数据库中有一个
Father对象，其关联有一个Son对象（bidir）。 - 从数据库父加载。
- 更新父亲的姓名字段。
- 更新儿子的姓名字段。
- 坚持父亲。
我的拦截器首先检测父亲更新（onFlushDirty）。然后为儿子执行onFlushDirty。在本例中，我更新了 son.lastModifyDate 和father.lastSonModifyDate。
执行结束时，除father.lastSonModifyDate 之外的所有更新都会保留。我认为这是因为父亲正在会话中并且已在儿子之前更新，因此该实体会覆盖儿子实体的 onFlushDirty 方法中所做的更改。
我怎样才能达到我的目标（从儿子拦截器设置父亲的lastSonModifyDate）？
谢谢。
My model:
public class Father {
Set<Son> sons = new HashSet<Son>();
String name = null;
Date lastSonModifyDate = null;
// ... other fields and setters/getters
}
public class Son {
Father father = null;
String name = null;
Date lastModifyDate = null;
// ... other fields and setters/getters
}
Use case:
- There is in DB a
Fatherobject with aSonobject associated (bidir). - Load from DB father.
- Update name field for father.
- Update name field for son.
- Persist father.
My interceptor first detects father updates (onFlushDirty). Then executes the onFlushDirty for the son. In this case, I update son.lastModifyDate and also father.lastSonModifyDate.
When execution ends, all updates are persisted except father.lastSonModifyDate. I think this is because father is in session and has been updated before son, so this entity overrides the changes done in onFlushDirty method for the son entity.
How could I achieve my mark (set father's lastSonModifyDate from son interceptor)?
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
你不能。 onFlushDirty() 是在为所有者调用 onFlushDirty() 并已计划更新操作（如果有）之后为集合元素调用的。
是否有任何原因导致您不能在 DAO 中执行上述所有操作而不是依赖拦截器？或者在数据库级别（映射生成的
lastModifyDate属性）？You can't. onFlushDirty() is invoked for collection elements after it has been invoked for owner and update action (if any) has already been scheduled.
Is there any reason why you can't do all of the above in your DAO instead of relying on interceptors? Or on the database level (mapping both
lastModifyDateproperties as generated)?您需要为具有级联选项的实体重写 onCollectionUpdate 。这是在安排之前调用的。
干杯~
you need to override onCollectionUpdate for entities that has cascading option. this is called before its being scheduled.
cheers~