To get a bidirectional association with a not-null foreign key column in the Details table you can add the suggested Owner property, a References(…).CanNotBeNull() mapping in the DetailsMap class, and make the Summary end inverse. To avoid having two different foreign key columns for the two association directions, you can either specify the column names … Read more
Ok, I found the answer. Add the not-found=”ignore” attribute to the property KeyField: <many-to-one name=”KeyField” not-found=”ignore” class=”Model.Entities.Key, Model” column=”field_id” />
I’ve seen decimal used instead of int/long in various examples. I’m just trying to understand why That’s probably because .NET decimal and Oracle NUMBER maps a bit better than long and NUMBER and it also gives you more flexibility. If you at a later stage add a scale in the Oracle column then you wouldn’t … Read more
Use collection interfaces instead of concrete collections, so NHibernate can inject it with its own collection implementation. In this case, use IList<int> instead of List<int>
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, … Read more