Verbalization Help #53
-
|
I can't seem to figure out how to correctly represent this relationship. For context, I am breaking up email addresses into two (Address@Domain) for storage. Storage(.ID) should have a one-to-one relationship with Address, but when I set it to be a one-to-one relationship, the constraint does not work (shows in red). The tables come out correctly with the setup you see in the picture, so in the end, it's not that big of a deal, but when AI reads the verbalization, it gives me a warning. Here is the verbalization. Email_Storage has Email_Address. For each Email_Address and Email_Domain, I need the bolded part to say "has exactly one", but when I get it to say that the text from the constraint goes away due to the error. Any help on this would be appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Nevermind. I just realized that it's correct the way it is. It would be possible to have user1@gmail.com and user1@outlook.com. My email address column could actually have two of the same. |
Beta Was this translation helpful? Give feedback.
-
|
Your answer is correct. Just a few errata looking at the model:
|
Beta Was this translation helpful? Give feedback.

Nevermind. I just realized that it's correct the way it is. It would be possible to have user1@gmail.com and user1@outlook.com. My email address column could actually have two of the same.