[backend] Improve objects resolutions for container (#4153)

[richard-julien]

No description provided.

[SouadHadjiat]

When I create an ObservedData from a domain name, it has the name of the domain name, then I add a note, there is no error anymore but the ObservedData name is now "empty".

===> update
I began to debug objects method which returns an empty list, and inside relations returns only one relationship with the domain name, and elements returns the note only. I guess the method should return both ?
=> it returns only one element because first argument is 1 in resolveName. So we only query 1 relationship and 1 element, but both are not the same.

[RomuDeuxfois]

Why are we retrieve elements from another query rather than retrieve them from the relations ?
We can have const toIds = relations.map((rel) => rel.toId) and resolve toIds, no ?

[richard-julien]

Its a general problem of the current model. In order to support case of pagination/sorting/filtering we use the denormalized id of elements stored in rel_. Unfortunalty we miss the fact that storing also the direction was needed and so when we list through that part we have sometime to much elements.

[RomuDeuxfois]

When I create an ObservedData from a domain name, it has the name of the domain name, then I add a note, there is no error anymore but the ObservedData name is now "empty".

===> update I began to debug objects method which returns an empty list, and inside relations returns only one relationship with the domain name, and elements returns the note only. I guess the method should return both ? => it returns only one element because first argument is 1 in resolveName. So we only query 1 relationship and 1 element, but both are not the same.

I test this case and it's fixed now

[RomuDeuxfois]

Tested 🆗