Here's a theoretical / pedantic question: there are good questions. Unfortunately, most of the answers I met seem to emphasize some third-party solutions.
Imagine a property in which each property can belong to several parties. In addition, from one iteration of the property to the next two neighboring territories, owners may decide to partially combine the property to .....
territory 1, t = 0: a, b, c, d territory 2, t-0: e, f, g, h
territory 1, t = 1: a, b, g, h territory 2, t = 1: g, h
That is, c and d no longer own property, and g and h become fat cats, so to speak.
Currently, I present this data structure as a tree, where each child can have several parents. My goal is to squeeze this into the composite data structure, but I am having problems with the conceptual basis of how the client can return and update the previous ownership without omitting the whole structure.
My question is twofold: Easy: what is a convenient name for this data structure so that I can do it myself?
Hard: What am I doing wrong? When I code, I try to keep the mantra: “Keep it simple, stupid,” in my head, and I feel that I am breaking this creed.
Thanks guys!