Announcement Announcement Module
Collapse
No announcement yet.
What is the impact of inverse=true, with no inverse property? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • What is the impact of inverse=true, with no inverse property?

    Let's say I had one table mapping with a "bag" marked as inverse=true. Typically, when I see that I expect to see in the mapping for the other side of this relationship an attribute that maps back to the class containing the bag.

    What does it mean when the class on the "other side" doesn't have that attribute?

    I'm looking at an example in some existing code, and I'm wondering what the impact of that would be.

    In the example I'm seeing, the "other side" has a composite primary key, where one of the components of that primary key is the "key column" referenced in the bag definition in the other class. I suppose this is the key point. This represents the other end of the relationship, correct? It seemed odd, as I hadn't seen an example before that does this.
    Last edited by dkarr; Jun 11th, 2009, 03:15 PM.
Working...
X