In my case, the generated SQL is attributing a field on the superclass table to the subclass when it is not there. I am seeing this on 3.6.10 with InheritanceType.JOINED. Is this the same problem or should I open a new bug?