hi RHS, thanks for the reply.
my intention is to build (let say) a Person app, it tracked addresses, names, personal_detail(marital_status, gender) of the person from time to time
I would like to make it more complete personal tracker to cater for
- Person will change name when they get married
- Person will move to different city(location) in different timeframe
So my app is sort of like
Parent table - person table (with only 1 field, person_id)
child table (with additional key field Effective_date) to track the ‘real’ him in a given date
that’s how i plan to design my app
master - Person table
detail - address, names, personal_detail (all of them have FK person_id, effective_date as keys)
With such design, i will no longer able to search for ‘person ever stay in London’ because my master table only contain person_id