Hibernate启用@Transactional时，插入数据@OneToMany字段为null，更新后为空？

Great question! This behavior is totally expected once you understand how Hibernate handles collection associations in different persistence states. Let's break down the two scenarios:

1. Why the field is null right after insertion #

When you insert a new entity with a @OneToMany field initialized to null:

• Hibernate doesn't automatically initialize empty collection associations for newly persisted entities unless you explicitly set it up. The entity starts as a transient object with your original null value, and Hibernate just persists that state to the database (since there are no child records to link anyway).
• Within the active @Transactional context, the entity remains in the persistence context, but Hibernate won't "invent" an empty collection instance for you here—it keeps the original null until something triggers a collection initialization.

2. Why it becomes an empty collection after update #

When you perform an update on the same entity:

• The update operation triggers Hibernate to either re-load the entity from the database or synchronize its state with the persistence context. During this process, Hibernate checks the associated child records.
• Since there are no child entries in the database, Hibernate will initialize the @OneToMany field to an empty collection instance (like ArrayList) instead of leaving it as null. This is a Hibernate design choice to help avoid NullPointerException when you try to iterate over or modify the collection later.

Quick Fix to Avoid Null Entirely #

The simplest way to make the behavior consistent (always get an empty collection instead of null) is to initialize the collection field directly in your entity class:

@OneToMany(mappedBy = "parent", cascade = CascadeType.ALL, orphanRemoval = true)
private List<ChildEntity> children = new ArrayList<>();

This way, whether you insert or update, the field will never be null—either it has child records or it's an empty collection.

Additional Notes #

• Double-check your @OneToMany mapping (ensure mappedBy is correctly set to the inverse side's field name if using bidirectional association).
• If you're using lazy fetching (fetch = FetchType.LAZY, which is default for @OneToMany), make sure you access the collection within the transaction context to avoid LazyInitializationException.

内容的提问来源于stack exchange，提问作者Govinda Raj