This works, except owing the unessential UPDATE “Lens” communiquВ. In my astuteness, since I’m using the GuidComb generator, NHibernate should delineate the Monicle_id in the INSERT “Lens” communiquВ. Instead, it’s inserting NULL, then updating it later. This prevents me from putting a NOT NULL constraint on Lens.Monicle_id. It’s been suggested that I acquire excess update, and I admit. I don’t acquire a one-to-many relationship to capsize it on.
However, the prescribed inverse=”true” won’t profession.
I’ve tried using HasOne quite than of References to conceive a bidirectional one-to-one relationship. It didn’t profession at all. My database schema didn’t disinterested acquire FK fields.