SUPPOSITION
Sometimes it is required for users to shape some kind of hierarchy. For example: group-group member relation or senior-junior relation. There are no support for user hierarchy in bootstrapi at the moment.
PROPOSITION
Let's introduce support for user hierarchy/relations for bootstrapi.
We can add new entity
user_relation
=============
id BIGINT
type INT
user_id_a BIGINT foreign key -> users.id
user_id_b BIGINT foreign key -> users.id
status INT
attributes JSON
Relation between users could be one of:
b created by a
b is a group member
a invitation located in attributes.data.invitation
... etc ...
Support for 'many-to-many', provided by external relations table, would allow, for example, to join users into multiple groups.
After some thinking, it looks like user relations would be more reasonable/consistent to implement based on connector-relation pair, not or separated user_relation table.
SUPPOSITION Sometimes it is required for users to shape some kind of hierarchy. For example: group-group member relation or senior-junior relation. There are no support for user hierarchy in bootstrapi at the moment.
PROPOSITION Let's introduce support for user hierarchy/relations for bootstrapi. We can add new entity
Relation between users could be one of:
b
created bya
b
is a group membera
invitation located inattributes.data.invitation
Support for 'many-to-many', provided by external relations table, would allow, for example, to join users into multiple groups.
PS. I can implement proposed update