You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In most frameworks, hasMany do this behaviour by default (return only ids), but when you pass { include: 'entity' }, it behave like embedded. What you think about it?
We are also using mongodb, and we have to either use hasManyThrough in those cases where referencesMany would be the obvious best choice according to mongodb data modelling best practices, or imitate referencesMany with custom repository methods. Either way it is inconvenient and has overhead costs.
If there are any details about the implementation of this feature, can you please share them ?
Also, can you recommend other workarounds besides the two I mentioned above?
Activity
alparslanyilmaaz commentedon May 8, 2020
achrinza commentedon May 8, 2020
mrbatista commentedon Nov 17, 2020
@bajtos Please assign the task to me.
spr1ne commentedon Dec 15, 2020
In most frameworks, hasMany do this behaviour by default (return only ids), but when you pass { include: 'entity' }, it behave like embedded. What you think about it?
hadnet commentedon Dec 16, 2020
Is this relation not implemented in LB 4 yet?
njtnestor commentedon Feb 21, 2021
I need this relation, when will be implemented? It is highly necessary to work with mongo
DavidKrpt commentedon Aug 10, 2021
We are also using mongodb, and we have to either use hasManyThrough in those cases where referencesMany would be the obvious best choice according to mongodb data modelling best practices, or imitate referencesMany with custom repository methods. Either way it is inconvenient and has overhead costs.
If there are any details about the implementation of this feature, can you please share them ?
Also, can you recommend other workarounds besides the two I mentioned above?
feat(repository): support `ReferencesMany` relation