If we save a new transient object with session.persist(...) followed by a flush afterwards a single INSERT-statement is executed as expected. But if the object's properties are changed between the session.persist(...) and flush an INSERT followed by an UPDATE are executed on flushing the session. We expect that only a single INSERT would be necessary to persist the entity instead of two statements.

Is this behaviour desired and what are the reasons for this.

BTW: We use manual flushing with long running conversation on disconnected session.

Thanks
Stefan

From my experience it is Hibernates 'write-behind' mechanism that works in this way.
When persisting a new object, an insert-event is queued with objects' snapshot of that moment of persisting.
Further changes on that object are then propagated with an update-event.



I assume it's desired, but unfortunately I don't know the reasons behind.
(In order to avoid the update, I already fill all properties with the final values before persisting the new object.)