Eclipse Community Forums: EclipseLink » Why tables for abstract classes with TablePerClass inheritance are created?

Help

Home

Home » Eclipse Projects » EclipseLink » Why tables for abstract classes with TablePerClass inheritance are created?

Show: Today's Messages :: Show Polls :: Message Navigator

Why tables for abstract classes with TablePerClass inheritance are created? [message #948359]

Thu, 18 October 2012 01:18

Rice Yeh

Messages: 20
Registered: July 2009

Junior Member

Hi,
Why table for an abstract class with inheritance strategy TablePerClass is created? Is not it that tables are created only for concrete classes for TAblePerClass inheritance strategy?

Rice

Report message to a moderator

Re: Why tables for abstract classes with TablePerClass inheritance are created? [message #950045 is a reply to message #948359]

Fri, 19 October 2012 15:22

Chris Delahunt

Messages: 1270
Registered: July 2009

Senior Member

Use a mapped superclass instead of marking it as an entity if you do not want a table for that class. I've been told that from a JPA perspective, entities can be used within queries, while mapped supperclasses cannot. So all entities require associated tables or they cannot be put within queries. Even though an abstract entity cannot be instantiated, queries using it could return raw data or to filter other entity results.

Best Regards,
Chris

Report message to a moderator