I'm attempting to store attributes common to 2 entities into 1 table (Table C) as per below diagram. The problem is that I can't maintain Referential Integrity. The Table C common attributes are enrichment data (i.e., data gets added to the base records in Tables A and B during a subsequent vetting/enrichment process). The cardinality between Table A and Table C is 1:1, and likewise between Table B and Table C. Is there a way to structurally handle this situation and still maintain Referential Integrity?
Thanks,
John