steckemetz wrote:
Perhaps you can use component mapping ?
See chapter 5.1.13.
I know component cannot have OID, but there is 3 individual businesses based on 1 table.
for example, a "Customer" table with many fields.
the login system only needs fields: ID, username, password.
the shoping system only needs fields: ID, truename, address, zipcode.
the email system only needs fields: ID, email.
maybe there will be new business needs other fields. e.g.: a blog system needs ID, blogTitle, articleCount, imageCount ...
these 3 class are not related but share the same primary key. also i don't want to use 1 class to hold all fields that may reduce performance.
can I use 3 classes but map them onto 1 table?