Update relationships.md

[Lalithkumarponnambalam]

Update relationships.md content

The following issue will be rectified:

• jhipster/generator-jhipster/issues/25584

I have referenced the "joint fields" from the JHipster Pro documentation. The correct link for the documentation is:

• JHipster Pro Documentation - Relationships with Joint Fields

[CLAassistant]

All committers have signed the CLA.

[netlify[bot]]

✅ Deploy Preview for jhipster-site ready!

Name	Link
🔨 Latest commit	04ce7e90b6edce573e63c02de563456cc33f99ff
🔍 Latest deploy log	https://app.netlify.com/sites/jhipster-site/deploys/65fc01e89e1e600008a135a3
😎 Deploy Preview	https://deploy-preview-1338--jhipster-site.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[OmarHawk]

Is this correct? To me the described syntax rather means "show name in any referencing attribute, like dropdown or list view link", the join will still always be executed based on the foreign key relationship afaik.

[Lalithkumarponnambalam]

@OmarHawk yes this is correct. In the JHipster Pro Documentation, there is an explanation of join fields in relationships, which can be found at the following link: JHipster Pro Documentation - Relationships with Joint Fields.

[OmarHawk]

Still not convinced. We are using the syntax and it works as I did describe. See also the syntax description here: https://www.jhipster.tech/jdl/relationships#syntax ---> <display field>

Also the .pro site looks kind of unofficial and rather outdated.

[mshima]

That’s not correct.

relationship OneToOne {
  A{b(name)} to B{a(name)}
}

means that when showing A, B will have b.name field as label (instead of b.id) in the frontend. Same for B. joins always use ids.

[mraible]

We updated the website with a new design. Can you please update this issue accordingly?

[mraible]

Closing due to lack of response.