In the relationship design view:
If a table T1 with a primary key t1_id is related to a table T2 with columns first_id, second_id, third_id; And three relationships are created T1.t1_id 1:n T2.first_id, T1.t1_id 1:n T2.second_id, T1.t1_id 1:n T2.third_id; Then only one of these relationships is displayed in subsequent edits. However, the relationships are known to exist because an error condition is raised if one attempts to add them again.
@James : please provide test odb file so that we can try and reproduce the behaviour, then reset to unconfirmed.
setting to needinfo pending requested information.
Created attachment 111789 [details]
LOBASE: simple base file showing n relationships from one tbl to multiple fields in another
This bug appears to be a different issue than I first imagined. The problem is not that additional relationships between the same two tables are not shown. The problem is that the additional relationships are not saved at all.
Created attachment 111790 [details]
screenshot showing multiple relations from one table to another
Created attachment 111791 [details]
screenshot of same relations ship display after saving and reopening
@James : if I go to the menu Tools > Relationships and try and create a new relationship by dragging and dropping from the first table id to the non-displayed FK id fields, I get an error message that the FK ref already exists, and asked whether I want to create a new one or edit the existing ref.
Is this also what you see ?
I can confirm that in the ODB file you provided the relations are not drawn in the relations window, yet they appear to be defined in the ODB file itself.
Confirming on master
Build ID: 6143a7eeabea394133c54e97e3690bdf40b98247
*** This bug has been marked as a duplicate of bug 45257 ***
Reading https://forum.openoffice.org/en/forum/viewtopic.php?t=67839, I gave a try.
When creating first relation, you can see cardinality ("1-n") but for the other ones created next, you don't see cartidinality.
You must explicitely name the constraints (only possible via SQL command in LO except)