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.

Given a structure such as : School -> Students -> PhoneNumbers

On Hibernate 6.4.4 and 6.4.9, I am observing the following odd behavior.

I have a MYSQL table that has 2 foreign keys to other rows of the same table. (for simplicities sake, I have changed it to a person table, that’s not what I am trying to achieve, but similar structure).

I’m mapping two entities 1:n where the many-side has a composite primary key. So far so good.

In my library project I have some JPA @Entity classes and a couple of JPA utils.

I use spring boot 2.7.18 with java 17 and maven. Please treat it purely for educational purposes (don’t shout at me that that’s not how filtering and updating should work, I know it). I’ve created that simple example after reading the article about ‘best way to handle hibernate MultipleBagFetchException’ and stumbled upon the problem with […]

I’ve done a lot of googling about this without much success, every time I look how people track bidirectional relations, it looks something like this:

I’m having an issue where a JPAentity I’m importing from another library has a field that’s hardcoded to be columnDefinition = TEXT but I’d like that field to be LONGTEXT in the db. I am not allowed to edit to the JPAentity itself, nor can I just make my own. Is there a way to force this via a custom dialect somehow?

I experience a strange behavior of the @Id field content in my app.
My entities are straight-forward: