Let’s say I have a Person entity which extends BaseLongIdEntity and uses the JOINED inheritance strategy. If I create two entities which extend Person, say Employee and Student, and then try to use a generic edit screen to create one instance of each of the derived entities, I get a Primary Key violation when trying to insert the second one in the database. (Demo project attached which illustrates the problem - try creating an Employee and then a Student instance - exception is thrown on the latter as it tries to insert into DEMO_PERSON using ID = 1.)
It seems CUBA is generating IDs based on the derived class type, ignoring the fact that the PK is actually controlled by the superclass.
This is obviously a major concern. Any idea how I can get around this?