@CreationTimestamp and @UpdateTimestamp with the same value after persistAndFlush

[hugo-testslick]

Describe the bug

Hi,

I'm using quarkus-hibernate-reactive-panache v3.6.4

After updating an entity both createdAt and updatedAt are returned with the the updatedAt value. However, createdAt is not being persisted to the database. When I list the records from the database the results are returned correctly. I'm using the same DTO object for both operations.

@Column(name = "created_at", updatable = false, nullable = false)
@CreationTimestamp
public LocalDateTime createdAt;

@Column(name = "updated_at", nullable = false)
@UpdateTimestamp
public LocalDateTime updatedAt;

Expected behavior

createdAt keeps the original value.

Actual behavior

createdAt is getting updatedAt

How to Reproduce?

1. persistAndFlush an existing entity that contains the createdAt and updatedAt described above
2. Check the result of the createdAt it gets exactly the same value as the updatedAt

Output of uname -a or ver

Darwin Kernel Version 23.2.0: Wed Nov 15 21:59:33 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T8112 arm64

Output of java -version

OpenJDK 64-Bit Server VM (build 21.0.1+12-29, mixed mode, sharing)

Quarkus version or git rev

3.6.4

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.8.6

Additional information

No response

[quarkus-bot]

/cc @gsmet (hibernate-orm), @yrodiere (hibernate-orm)

[yrodiere]

Thanks for reporting.

@hugo-testslick this doesn't look specific to Quarkus, can you please provide a reproducer based on https://github.com/hibernate/hibernate-reactive/tree/main/examples/session-example ?

@DavideD I think Hibernate Reactive overrides ID generators, does it also override support for creation timestamp and update timestamp? Could this be specific to HR, or is this necessarily a problem in ORM?

[hugo-testslick]

@yrodiere thank you for your answer.

I'm not able to replicate it in https://github.com/hibernate/hibernate-reactive/tree/main/examples/session-example.

Maybe this is related with Panache implementation?

The same operation return the correct result if persistAndFlush is not invoked previously otherwise createdAt is always overiden even when creating a new session.

[yrodiere]

I'm not able to replicate it in https://github.com/hibernate/hibernate-reactive/tree/main/examples/session-example.

Can you please share a reproducer using Quarkus then?

Maybe this is related with Panache implementation?

Sounds unlikely considering how light the Panache stuff is when it comes to persisting, but maybe.

[hugo-testslick]

@yrodiere I found a way to reproduce the issue seems to be related with having both @CreationTimestamp and @UpdateTimestamp on a @Embeddable class. This happens when updating the entity. The update endpoint returns the createdAt overridden. Example below the createdAt value at the database is 2024-02-28T19:04:25.276429 but the updated entity gets returned as:
{ "id": 4, "name": "Test123", "audit": { "createdAt": "2024-02-28T19:04:37.024818", "updatedAt": "2024-02-28T19:04:37.024843" } }
https://github.com/hugo-testslick/39016

[yrodiere]

Thanks for the reproducer, I'll let @DavideD or @gavinking have a look when they have some time.

[hugo-testslick]

Thanks @yrodiere, @DavideD, @gavinking any update on this?

[SilverSilence]

Any update on this?