NHibernate 中的逆属性

小开

最佳答案

The inverse attribute must not be set to true ...

You use the inverse attribute to specify the 'owner' of the association. (An association can have only one owner, so one end has to be set to inverse, the other has to be set to 'non inverse'). (Owner: inverse=false; Non-owner: inverse=true)

In a one-to-many association, if you do not mark the collection as the inverse end, then NHibernate will perform an additional UPDATE. In fact, in this case, NHibernate will first insert the entity that is contained in the collection, if necessary insert the entity that owns the collection, and afterwards, updates the 'collection entity', so that the foreign key is set and the association is made. (Note that this also means that the foreign key in your DB should be nullable).

When you mark the collection end as 'inverse', then NHibernate will first persist the entity that 'owns' the collection, and will persist the entities that are in the collection afterwards, avoiding an additional UPDATE statement.

So, in an bi-directional association, you always have one inverse end.

小开

In addition to the answer above, and according to my understanding, you need to persist the foreign key value in the collection manually, that is if you don't want the extra update statement:

Parent par = Session.Get<Parent>(8);


Child ch = new Child();
ch.Name = "Emad";


//set the parent foreign key manually
ch.MyParent = par;


par.MyChildren.Add(ch);
Session.Save(par);

for further explanation of the inverse attribute, check the following post:

http://www.emadashi.com/index.php/2008/08/nhibernate-inverse-attribute/

小开

I can see where the "owner" comes in, but an association is a pipe, and you can look down either end, so whats to say which entity "owns" the pipe.

A different way of looking at this is, that in a One to Many relationships, there are actually 2 relationships going on.

Relationship 1: Parent to Many Children.

Relationship 2: Each Child to a Parent

So NH will attempt to run sql to store each of these in the DB. But it doesn't need to because when you set the Foreign Key e.g. in Relationship 2 when a child is stored, then it automatically has fixed the relationship of a parent to the child as well because Relationship 1 is the "Inverse" of Relationship 2.

So inverse means, its something that we get by default once we've set the main relationship. i.e. there is no need for NH to run sql to fix up Relationship 1 and by marking the children collection as an Inverse NH will skip running sql when the children collection is added to.

I'd assume that if you didn't tell NH it was an inverse, then it would waste effort in doing sql to try and set in place the inverse relationship as well - even though it didn't need to.