Issues

Select view

Select search mode

 
21 of 21

Association override validation wrongly fails for union-subclass strategy

Won't Fix

Description

An entity model like the following fails since 6.5:

fails with:

Details

Assignee

Reporter

Sprint

Affects versions

Priority

Created June 11, 2024 at 10:52 PM
Updated June 12, 2024 at 9:41 AM
Resolved June 12, 2024 at 9:38 AM

Activity

Show:

Gavin KingJune 12, 2024 at 9:41 AM

nope, I agree, not worth it

Christian BeikovJune 12, 2024 at 9:38 AM

Looks like I was wrong and ORM 5 did not support this either. It also looks very complicated to support, so not sure if it's worth it.

Gavin KingJune 11, 2024 at 11:23 PM
Edited

As far as I can tell, if you disable that error, we simply ignore the @AssociationOverride annotation. So it might appear to the user that their @AssociationOverride is working, when it is in fact not doing anything.

Gavin KingJune 11, 2024 at 11:06 PM

If this error is wrong, Iā€™m impressed, and apparently we can do things I really didn't think we could do!

But, hear me out: when you query against TablePerClassBase do we really generate the correct SQL in this case? We would need to populate the association by joining both tpces1_list and tpce_list, since other concrete subclasses would inherit the un-overridden mapping.

Flag notifications