Strategy for implementing a composite key of which the second part is rarely discriminating. Entity Framework Code First

Question

I have the following scenario:

An Atom Entity is usually unique and can be stored in the database using a single AtomID field as its primary key.. In rare cases theAtomneeds to be split. In that case a second record must be created in the database table with an identicalAtomIDbut a discriminatingSplitID`.

So, basically I need a composite key of AtomID and SplitID where the SplitID will rarely be discriminating. I would hate to lose the AutoID feature that the SQLServerCompact4 database offers, but that is what happens when I define a composite key for the Atom Entity in the Fluid API.

What is the best approach for this problem?

Answer 1

You should create a new table with foreign key , AtomID and the discriminating SpiltID to show the relation between the two.