Yeah, that makes sense. It is just deviating behavior from Hibernate 5.6 which is why it popped up for me. Was probably working “by accident”.