table-per-class

I am using the table per subclass strategy in Grails by setting the tablePerHierarchy property of the static mapping field in my superclass to false. This way, Grails creates one table for my superclass and one additional table for each of my subclasses. However, while the superclass and subclass records share the same ID (primary key), there are no foreign key constraints to keep them consistent, i.e. it is possible to delete the superclass record, leaving the subclass record in an invalid state. I want to know if there is a setting/property to make GORM address this in some way, e.g. through

i have the following scenario public abstract class BaseClass { public virtual int Id {get; set}; public virtual string Name {get; set;} } public class FirstSubClass : BaseClass { //properties and behaviour here } public class SecondSubClass : BaseClass { //properties of SecondSubclass Here } public class ProcessStep { public virtual IList<BaseClass> ContentElements {get; set;} } for mapping i have used following code snippet :- this._sessionFactory = Fluently.Configure().Database(SQLiteConfiguration.Standard .ConnectionString(@"Data Source=SqliteTestSqlDataAccess.s3db; Version=3; New=True;

I'm using EclipseLink as the JPA provider. Further I'm using the following TABLE_PER_CLASS inheritance structure @javax.persistence.Entity @Inheritance(strategy = InheritanceType.TABLE_PER_CLASS) @NamedQueries({ @NamedQuery(name=Parent.QUERY_FIND_ALL, query="SELECT p FROM Parent p") }) public class Parent { // the class code follows here } @javax.persistence.Entity @NamedQueries({ @NamedQuery(name=Child.QUERY_FIND_ALL, query="SELECT c FROM Child c") }) public class Child extends Parent { // the class code follows here } The problem now is that I only want to receive entries of the parent class

I'm using Hibernate JPA. Suppose I have these classes: AbstractPerson |--> ConcreteEmployee |--> ConcreteCustomer Is there any way to make the concrete classes have independent IDs? I'm using InheritanceType.TABLE_PER_CLASS. From the Hibernate Annotations Reference Guide: 2.2.4.1. Table per class This strategy has many drawbacks (esp. with polymorphic queries and associations) explained in the JPA spec, the Hibernate reference documentation, Hibernate in Action, and many other places. Hibernate work around most of them implementing this strategy using SQL UNION queries. It is commonly used for