Strange behaviour with UUID key generators in spring-data-jpa-auditing

[jvmlet]

Hello
Thanks for the greate tutorial
I'm experience the interesting issue if I change the id from Integer to UUID in File class in spring-data-jpa-auditing project :

    @Id
    @GeneratedValue (generator = "UUID")
    @GenericGenerator(            name = "UUID",
            strategy = "org.hibernate.id.UUIDGenerator"
    )
    private UUID id;

The exception I'm getting is :

Caused by: org.springframework.dao.DataIntegrityViolationException: could not execute statement; SQL [n/a]; constraint ["PRIMARY_KEY_2 ON PUBLIC.FILE(ID) VALUES (X'1797c3aded61453d891874d491356c9c', 1)"; SQL statement:
insert into file (created_by, created_date, last_modified_by, last_modified_date, content, name, id) values (?, ?, ?, ?, ?, ?, ?) [23505-197]]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute statement

And I see two insert statements for File entity.
To reproduce, just change the id to be UUID with the annotations I've shown before ,tweak getter and seeter ,change from @PrePersist to @PostPersist :

public class FileEntityListener {

    @PostPersist //  @PrePersist 
    public void prePersist(File target) {
        perform(target, INSERTED);
    }
}

and run.
Can you think about the reason and possible solution ?
Thanks

[njnareshjoshi]

@jvmlet , It is really a strange behavior and it is happening because when we are trying to save FileHistory record in FileEntityListener class hibernate is trying to save file record again with the same id.

And that's why there are two insert statements and that's why we are getting java.sql.SQLIntegrityConstraintViolationException: Duplicate entry '\xE4\xC3\xD6&\xE5\xF0H\xFC\x873j\x02k\xA5\xEC\xD1' for key 'PRIMARY'

However the same is not happening when we are using int id instead of uuid.