First of all, good research
Yes, this was raised as a bug previously with Hibernate , and has also been fixed. But due to the lack of test cases, it was rejected and was never released as part of subsequent releases.
The error was introduced as part of Hibernate 3.6 .
Therefore, you still need to wait until someone raises a ticket, and provide suitable test cases and fix it.
refer here for more details.
source share