Rohit Vats

Would also be very useful to allow apps to be mapped individually, so that users can select ratings for each app separately.

We could add nullable `old_value` and `new_value` fields, but in cases where multiple fields updated together, populating these might not make sense.

Yes, this will result in too many relationship tables, which may not be ideal. Although the generic `entity_relationship` table is also not perfect because the ordering of entities is enforced...

@davidwatkins73 , agreed about multiple relationships, eg: App can have both functional/non-functional changes delivered under a CI. I guess a decorator table will make this cleaner, instead of repeating child...

Looks like we are going with option 1, a different `relationship_kind` table is good, it also helps us externalise the rel kinds, so they can be customised without a core...