I am working on an application consisting in a high-throughput entity, where I need to mitigate race conditions, and some unfrequently-changed domain entities.
To achieve this, we added JPA optimistic locking to the existing application.

If the entity persisted in transaction is further modified, then the @CreationTimestamp field will become null. Are there any solutions to this problem? Magic hibernate flags? Or do we only have to create the field manually in the @PrePersist method? I also don’t want to flush the data after the persist method, as this is an unnecessary database call.

If the entity persisted in transaction is further modified, then the @CreationTimestamp field will become null. Are there any solutions to this problem? Magic hibernate flags? Or do we only have to create the field manually in the @PrePersist method? I also don’t want to flush the data after the persist method, as this is an unnecessary database call.

If the entity persisted in transaction is further modified, then the @CreationTimestamp field will become null. Are there any solutions to this problem? Magic hibernate flags? Or do we only have to create the field manually in the @PrePersist method? I also don’t want to flush the data after the persist method, as this is an unnecessary database call.

If the entity persisted in transaction is further modified, then the @CreationTimestamp field will become null. Are there any solutions to this problem? Magic hibernate flags? Or do we only have to create the field manually in the @PrePersist method? I also don’t want to flush the data after the persist method, as this is an unnecessary database call.

If the entity persisted in transaction is further modified, then the @CreationTimestamp field will become null. Are there any solutions to this problem? Magic hibernate flags? Or do we only have to create the field manually in the @PrePersist method? I also don’t want to flush the data after the persist method, as this is an unnecessary database call.

If the entity persisted in transaction is further modified, then the @CreationTimestamp field will become null. Are there any solutions to this problem? Magic hibernate flags? Or do we only have to create the field manually in the @PrePersist method? I also don’t want to flush the data after the persist method, as this is an unnecessary database call.

If the entity persisted in transaction is further modified, then the @CreationTimestamp field will become null. Are there any solutions to this problem? Magic hibernate flags? Or do we only have to create the field manually in the @PrePersist method? I also don’t want to flush the data after the persist method, as this is an unnecessary database call.

If the entity persisted in transaction is further modified, then the @CreationTimestamp field will become null. Are there any solutions to this problem? Magic hibernate flags? Or do we only have to create the field manually in the @PrePersist method? I also don’t want to flush the data after the persist method, as this is an unnecessary database call.

If the entity persisted in transaction is further modified, then the @CreationTimestamp field will become null. Are there any solutions to this problem? Magic hibernate flags? Or do we only have to create the field manually in the @PrePersist method? I also don’t want to flush the data after the persist method, as this is an unnecessary database call.