Quote:
Originally Posted by DBNull
First time poster on DBForums.com, Hello @ All.
So by having this secondary key I can update parent records without cascading updates to the child records.
|
I am not clear on this design and the need to have many parent records with a current status to distinguish historical rows. Why would you need to do cascading updates/deletes on the child record if the parent changed? Isn't the relationship still coherent without the necessity of creating new parent records? If the parent changed does this mean the relationship with child records is no longer valid?