Transient child (using new Child and child.setParent(parent)) persistence created out of a detached parent (hibTemplate.find("from Parent")) does a separate select on each parent when inserting child.

Tried both bidrectional mapping with mappedBy on OneToMany side to make it bidrectional and also a separate mapping to make it unidirectional after removing mappedBy.

Also tried selecting parent from statless and stateful sessions. Nothing stops from running a separate select on the parent when persisting child.

Beginning to realize that in our Spring batch application, although parent source returns detached objects using stateless session which is flushed and cleared well by Spring batch reader itself, the overall transaction boundary encompasses both the parent object reader and persistence in our dao where we persist new transient collections associated with this detached parent. Hibernate is trying to fetch its parent again to confirm this parent exists because of the bi directional relationship and the only solution I see is creating a proxy out of this parent while persisting children yet again :(.

I was also assuming making insertable=false on OneToMany annotation and setting optional=true, then persisting by separate column mapping will not check, but that is not the case at all. Its doing a separate select of the parent just before the spring batch transaction boundary commits/flushes.

Isn't there any ways of mentioning that the relationship is just for join purpose and nothing else??