Support multiple labels / default label

[lomoval]

Do you have any plans of supporting multiple labels for nodes (structures) or some default(main) label for struct?

GOGM uses first label of node.
This leads to difficulties if additional labels are used.
For example:

n1:Sensor
n2:Active:Sensor

The main label/entity is Sensor. In both cases it will be useful to load struct by GOGM (without any raw queries). But currently for the second case you need to have Active struct that is same as Sensor (with same links and etc).

Some config for structs with main labels or with ignoring labels by GOGM will be really useful.

[erictg]

Hi,
This is a a cool feature but it currently isn't on our road map. We might look into this in the future, but currently have no plans in place to implement it. If you want to try to implement this, i'd be happy to give some guidance!

[palandlom]

... thinking of this feature - go-structure composition can be used:

type Entity struct {
	gogm.BaseNode
	DomainId string `gogm:"name=seId;pk=DomainId"`
}

type Agent struct {
	Entity
	AgentName string `gogm:"name=agentName"`
}

in that case a := gogm.Agent would be node with 2 labels :Agent :Entity

[nikitawootten]

@palandlom this would be really cool, but I feel like it could lead to some really weird edge cases. Like if one node had a relationship to another node but that node had multiple labels and the relationship was a subtype (like Agent in your example), how should gogm go about parsing it? Should it throw away the extra information?

Although struct composition would be more elegant, I think the easier solution would be to have a reserved list of labels that have special meaning.

[palandlom]

Like if one node had a relationship to another node but that node had multiple labels and the relationship was a subtype (like Agent in your example), how should gogm go about parsing it? Should it throw away the extra information?

So some node has >1 label - e.g. n:Agent, Entity
From the first site we have the following cases:

1. case - We have another node with 1 label - e.g. o:Organization + this node has edge to previous node with 2 labels - e.g o:Organization-HAS_MEMBER->n:Entity

2. case - ... in addition to the edge from 1case - we also have edge to "subtype" of :Entity - e.g o:Organization-HAS_DIRECTOR->n:Agent

IMHO:
in 1-case (i.e. when we get members of some organization) gogm should interpret n:Agent, Entity as only as :Entity - i.e. get only properties/edges that are relevant to fields of gogm-struct Entity {...}

in 2-case (i.e. when we get directors of some organization) gogm should interpret n:Agent, Entity as :Agent and :Entity - i.e. get properties/edges that are relevant to fields of gogm-struct Agent {...} and also fields of "included" gogm-struct of Entity.

[nikitawootten]

I'm going to convert this issue to a discussion.