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
Hi @dplewis , thanks for quick reply & implementation.
I tried your code change and it's work by appending _p_.
the thing I notice, the form of aggregate query is not consistent with the form of relational query ( a query using keyword where ).
for my query above , here is the change I made to make it work.
@xedixermawan In mongo especially there are multiple stages (20+) for aggregates so adding transforms for all of them would take some time. I guess we can transform the main 3 group, match, project. You want to open a PR to add pointer transform to match? I'll review it
Activity
dplewis commentedon Jan 9, 2018
A quick workaround is appending
_p_to the field name (Mongo)Edit: Postgres Supports
{ group: { objectId: '$pointerFieldName' } }works out of the boxdplewis commentedon Jan 9, 2018
Closed via #4493
xedixermawan commentedon Jan 9, 2018
Hi @dplewis , thanks for quick reply & implementation.
I tried your code change and it's work by appending
_p_.the thing I notice, the form of aggregate query is not consistent with the form of relational query ( a query using keyword
where).for my query above , here is the change I made to make it work.
dplewis commentedon Jan 9, 2018
@xedixermawan In mongo especially there are multiple stages (20+) for aggregates so adding transforms for all of them would take some time. I guess we can transform the main 3
group,match,project. You want to open a PR to add pointer transform tomatch? I'll review it