Annoyance 5.75: No 1:1 relation possible
Posted: 2019-06-24 17:02
Hi,
I asked here ( viewtopic.php?f=2&t=3038&p=10340#p10112 ) if a 1:1 relation is possible, and it seems that this is not the case yet.
As this might be an error made by the user when creating the application in AG a warning seems to me better than to show an error. I actually want my PK to show up in a second table (be FK) and want it to be unique so create a 1:1 relation.
I do not really see a reason, even thinking about your internal coding, why this is forbidden - so, I ask you to make this possible.
Why this is "important" too: If I change the field in the database to unique I get the desired, but the application will always show it as a mismatch between AG definition and actual DB.
Thanks
Olaf
I asked here ( viewtopic.php?f=2&t=3038&p=10340#p10112 ) if a 1:1 relation is possible, and it seems that this is not the case yet.
As this might be an error made by the user when creating the application in AG a warning seems to me better than to show an error. I actually want my PK to show up in a second table (be FK) and want it to be unique so create a 1:1 relation.
I do not really see a reason, even thinking about your internal coding, why this is forbidden - so, I ask you to make this possible.
Why this is "important" too: If I change the field in the database to unique I get the desired, but the application will always show it as a mismatch between AG definition and actual DB.
Thanks
Olaf