I am mapping a table using "table-per-hierarchy". When I search by the ID, I am able to get one subclass(SubA) loaded correctly, but get a WrongClassException when trying to load a object which should be loaded to the 2nd subclass(SubB). Below is the hibernate mapping(having removed additional properties) and exception stack. Not sure if this matters but the mappings for individual classes are in separate files.

From the exception it looks like its trying to load Product object instead of SubB, although, it has identified the discriminator correctly as ABC.

With this mapping when I search for a products SubA is found correctly, but I SubB doesnt get picked up correctly with WrongClassException.

Folks,

I was able to find a workaround. The column in the table for discriminator is defined as char(4). I changed the discriminator for SubB from ABC to ABCD and it works.

Is this a known limitation when using discriminators? Is this a know limitation when using char(4) instead of say varchar or int?

Would be great to have a confirmation if this indeed is a limitation.