Are you an IT Pro with some training on DBs and data structures knowing exactly what you want? I ask that because I understand your intention but I don’t understand your contents and possible data conflicts. People without proper training learn the hard way about data conflicts and data synchronization.
Maybe you could explain a bit more what you are wanting to achieve? Or you may learn now something.
Let me tell you a problem I saw few years ago, someone requested something like what you want and I denied to give them what they wanted as they wanted. They had a distributed offline data acquisition, where sales people could contact some people and request some data from them generating 1 very simple person record, like [rowid, name]; and many data recs as [rowid, person_id, date_time, data], many times along multiple days.
This very simple system (made by the owner years before) was already in use, and…it was a single-user system. One user only, an operator, who knew all those people providing the data by name, so they used just the name as the identifier, and received new infos on paper to type, then the operator located the proper “person” record, and then he entered new data when new forms arrived. Like a sheet for “Samuel Quinn”, “A2345”, “B23452”; “Allison jones”, “F238447”, “J28848”, “P28882”
Then someone thought “we could make an exact offline data entry, people could collect the data, then later we just merge all data automatically!”. Can you spot the problem?
Let me say another info, people could write the name freely in the form, sometimes “Samuel Quinn” could appear as “Sam Quinn” or “Samuel Queen”, but the operator fixed that at typing time (or not) I’ve found cases like Samuel Nicholas Quinn and Samuel Quinn coexisting but they were the same person. (The names and data here are fictional)
There were more problems than just that, I just said part of the problems to you understand my concerns.