| I'm running 5.2.10 and I still see an issue. If an entity has multiple lazy properties but not all of them have been loaded, hasUninitializedLazyProperties() returns true, and then getUpdateStrings() selects the lazy update SQL statement, which does not update any of the lazy properties: private String[] getUpdateStrings(boolean byRowId, boolean lazy) {
if ( byRowId ) { return lazy ? getSQLLazyUpdateByRowIdStrings() : getSQLUpdateByRowIdStrings(); } else { return lazy ? getSQLLazyUpdateStrings() : getSQLUpdateStrings(); } } It seems that there should be a check around here to see if only some of the lazy properties are initialized and others are dirty and activate Dynamic Update: if ( entry == null && !isMutable() ) { throw new IllegalStateException( "Updating immutable entity that is not in session yet!" ); } if ( ( entityMetamodel.isDynamicUpdate() && dirtyFields != null ) ) {
// We need to generate the UPDATE SQL when dynamic-update="true"
propsToUpdate = getPropertiesToUpdate( dirtyFields, hasDirtyCollection );
// don't need to check laziness (dirty checking algorithm handles that)
updateStrings = new String[span];
for ( int j = 0; j < span; j++ ) { updateStrings[j] = tableUpdateNeeded[j] ? generateUpdateString( propsToUpdate, j, oldFields, j == 0 && rowId != null ) : null; } } |
