in

The ORM Foundation

Get the facts!

1 to 1 between Entities when Mandatory

Last post Wed, Jan 30 2008 19:37 by Taber_Loveless. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • Tue, Jan 29 2008 20:44

    1 to 1 between Entities when Mandatory

    Verbalization of column names does not work properly for a 1 to 1 fact between entities when a role is Mandatory. 
    
    To get around this, I found that I must set the "Name" value on the mandatory Role of the fact.
  • Wed, Jan 30 2008 12:47 In reply to

    • Kevin M. Owen
    • Top 500 Contributor
      Male
    • Joined on Sun, Nov 18 2007
    • Neumont University, South Jordan, Utah
    • Posts 0

    RE: 1 to 1 between Entities when Mandatory

    Could you please post what the verbalization is currently coming out as, and what part of it is wrong (if it is not obvious)? Thanks.
  • Wed, Jan 30 2008 13:43 In reply to

    RE: 1 to 1 between Entities when Mandatory

    Company(code) ___*-|-___ Subscription(Nr)
    
    verbs as:
    Company has DriverTech Subscription.
    Each Company has exactly one DriverTech Subscription.
    For each DriverTech Subscription, at most one Company has that DriverTech Subscription.
    
    but Database table:
    Company (Company_Code, Company, ...)
    
    UNLESS I provide a name for the Role marked as Mandatory (*)
    
    See the model I posed under General Discussion on the "Core" page (youll have to remove the role name).
  • Wed, Jan 30 2008 17:08 In reply to

    RE: 1 to 1 between Entities when Mandatory

    Also:
    
    When a role is set as Mandatory the constraint name in the Relational View becomes "Constraint" instead of "InternalUniquenessConstraintXX".
  • Wed, Jan 30 2008 19:37 In reply to

    RE: 1 to 1 between Entities when Mandatory

    Here is an image to illustrate the previous post:
    
    http://netstatworks.com/media/Constraint-Name-Issue-with-Mandatory_1to1-or-Entities-involved-in-SubTyping.JPG
Page 1 of 1 (5 items)
© 2008-2024 ------- Terms of Service