In my app I have a meeting object with its properties stored in a meeting table. I have to create a new object, let's say "meetingNEW" having some different properties, but most of them common.
I'm thinking to use the table per concrete class strategy, but I'd like to have separate ids for the two tables and not inherit it from the superclass. Is it possible? I'm only finding examples with a common id.
My idea is: MeetingType -> abstract superclass
Meeting extends MeetingType with Meeting_id as PK (table)
MeetingNEW extends MeetingType with meetingNEW_id as PK (table)
Thanks
Why do you use Table per concrete class strategy ? For me it seems like table per subclass strategy like below with meeting_type table with common properties and other tables with specific properties with its own PK id.