[hibernate-issues] [Hibernate-JIRA] Issue Comment Edited: (HHH-5797) Improve batching for entity updates or deletes that use secondary tables

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5797?page=c... ] Steve Ebersole edited comment on HHH-5797 at 1/4/11 2:09 PM: ------------------------------------------------------------- I have a preliminary idea about using an interface {{Operation}} to help here. The idea would be that a {{Batch}} is composed of a series of {{Operation}} instances instead of a series of {{PreparedStatement}} instances as it is today. The underlying trouble here is the possibility that existing rows in the secondary tables may not exist (legacy data). Therefore instead of an {{UPDATE}}, for example, in the secondary table we may instead need to issue an {{INSERT}}. However, we do not know that until after the {{UPDATE}} has been attempted. It is this situation of "multiple statements" that is being addressed here. was (Author: steve): I have a preliminary idea about using an interface {{Operation}} to help here. The idea would be that a {{Batch}} is composed of a series of {{Operation}}s instead of a series of {{PreparedStatement}}s as it is today. The underlying trouble here is the possibility that existing rows in the secondary tables may not exist (legacy data). Therefore instead of an {{UPDATE}}, for example, in the secondary table we may instead need to issue an {{INSERT}}. However, we do not know that until after the {{UPDATE}} has been attempted. It is this situation of "multiple statements" that is being addressed here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira