Referential integrity constraint violation about activate HOT 6 CLOSED

Shouldn't Geoloc be abstract? The FK is pointing to the Geoloc table and the insert is done in the Country table.

from activate.

If it is abstract there is no error. But what about situation, when Geoloc is not abstract?

from activate.

If the Geoloc isn't abstract, it is necessary to remove the FK since relational databases don't support FKs to multiple tables.

from activate.

JPA can handle such situation. Are you planning to implement the feature? Since IDs are unique there shouldn't be a problem. :).

from activate.

Activate has support for this scenario, but the database can't have a FK that points to more than one table, so you have to drop it.
I don't think that JPA can create a FK that points to more than one table. It is a database limitation. :)

from activate.

Afterthought, JPA can hadle this scenario if you store multiple concrete entities types in the same table.
It is possible to implement in Activate, but I don't see this functionality prioritized in the roadmap.

from activate.