Replies: 2 comments
-
This is working now. Seems some of my changes fixed this. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Please see my latest comment in #1447 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I hope i'm explaining this correctly
We have a model called
Client
.A client can have multiple retailers (which are also clients).
A client can have multiple suppliers (which are also clients, defined if a client has retailers)
So a Client has one or many retailers, which then result in one ore more suppliers for a client.
Now we want to look up the inverse of this relationship.
So when we have a Client which is actually a retailer. We want to look up all suppliers this client/retailer has.
So we defined the inverse relation for retailers.
The result:
Meshed-up data and primarykey in the ClientRetailer. So we can't determine the relations anymore.
What are we missing?
Is this even posible?
Beta Was this translation helpful? Give feedback.
All reactions