Im confused with many-to-many relation. Why no “cross_table” is created?

@nosykretts There’s no need for a cross or lookup table because GraphQL is able to keep track of the relations directly. So if you queried a node that contained a many-to-many relationship the result in that relationship would come back as an array of objects.

I need to add field beetwen the m:n relation.

Could you post an example of the schema you’re wanting?

I have Patient, Exam, and Branch Type. Branch m:n Exam My business logic is. Every Branch may have different Exam pricing.

Got it! If I understand correctly, then you would want to set up your Nodes like this:

type Patient implements Node {
  exams: [Exam!]! @relation(name: "ExamOnPatient")
  name: String!
  etc.
}

type Exam implements Node {
  price: Int!
  branchTypes: [BranchType!]! @relation(name: "BranchTypeOnExam")
  patient: Patient! @relation(name: "ExamOnPatient")
  etc.
}

type BranchType implements Node {
  name: String!
  exams: [Exam!]! @relation(name: "BranchTypeOnExam")
  etc.
}

wait a minute. I need time for processing that info 😁

Sorry, hit Enter instead of Shift-Enter at first. It’s all there now.

I experimenting with your suggestion. need little time #youAreFast #ImSlowLearner 😃 👍

No problem!

@yergi If I understand correctly. suggestion you give me Branch and Exam still m:n relation?

Yes, it’s still a many-to-many relationship. Is that not what you need?

yes. but I still cannot set price on exam based on different branches

Since

price

is a field of

Exam

, whatever your system is where you’re creating the mutation calls to create new data should be able to set the

price

field based on the branches you’re relating the new data to.

so your suggestion I can create this? Branch A - Exam1 : 1200 - Exam2 : 1300 Branch B - Exam1 : 1900 - Exam2 : 1400

That’s right.

so my exam type is not unique?

What I gave you is the schema; you’ll still need to work out the logic in your solution on how to create the mutation calls to create new exams based on branch.

yes. every item on exam name should unique.

🤔

Yes. thats is my original question. I should make my own cross_table.

Yes, sorry. I misunderstood what part needed to be unique.

But. Im very thankful you help me out 👍

@nosykretts @yergi did you resolve this? Happy to help you out here 🙂