Thanks for replying, I am aware of Hibernate.isInstance() and Hibernate.unproxy() methods but if possible I’d like to be able to write idiomatic Java code, for instance:

if (food instanceof Cheese cheese) {
    // use the cheese
}

Instead of:

if (Hibernate.isInstance(food, Cheese.class)) {
	Cheese cheese = Hibernate.unproxy(food, Cheese.class);
	// use the cheese
}

One benefit of having the right class is that we wouldn’t need to trigger a load if we just need an instanceof test.

I’ve got to admit that I’m not familiar with @Any so I’ll look into that 👍

Some of the associations I have are collections fetched using the new `@SQLSelect` so I’m sure sure if that scenario would be supported.

Assuming that item now needs a discriminator, I would need to tell Hibernate where that new column would be, but JPA’s @FieldResult` does not support it, right?

   @SqlResultSetMapping(name="OrderResults",
       entities={
           @EntityResult(entityClass=com.acme.Order.class, fields={
               @FieldResult(name="id", column="order_id"),
               @FieldResult(name="quantity", column="order_quantity"),
               @FieldResult(name="item", column="order_item")})
       })