Hi, has this issue been fixed in a subsequent release of hibernate? I tried 5.4.32 and it is still present. This is preventing me from upgrading past Hibernate 5.4.19. Seems like a relatively significant bug and may not be noticed by most users since the behavior for typical functional tests would indicate that there is nothing wrong.