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
As you can see 'customer-1' is member of both Shop1 and Shop2
Problem is - if I don't define reverse relation for Customer in Shop, and do not tell Customer to save parent id, it never adds Customer model into Shop's collection, despite Shop model having necessary IDs of children and making all necessary requests. From reading code it seems like expected child model to add itself into parent collection.
Few questions:
are my observation correct?
is there particular reason for this design?
should I implement this change and submit PR or someone else already working on fixing that?
The text was updated successfully, but these errors were encountered:
I am having schema where multiple children might have multiple parents. I actually found correct example in test:
Shop1.customers = ['customer-1', 'customer-2']
Shop2.customers = ['customer-1', 'customer-3']
As you can see 'customer-1' is member of both Shop1 and Shop2
Problem is - if I don't define reverse relation for Customer in Shop, and do not tell Customer to save parent id, it never adds Customer model into Shop's collection, despite Shop model having necessary IDs of children and making all necessary requests. From reading code it seems like expected child model to add itself into parent collection.
Few questions:
The text was updated successfully, but these errors were encountered: