Composite-Id relationships (key-many-to-one) do not appear to be used in CreateCriteria

Wish there was a way to delete or edit a comment .

Turns out my mapping had the CompositeId defined with a KeyReference and then (at least up to 3.3.1) we also had a mapping for the reference defined to get around this bug and once the fix for this was in place AND I removed that additional reference mapping, the issues we were seeing went away. No new bug but others that experience this should remove the additional Reference mapping.

Unfortunately this fix now causes another issue of duplicate joins when the query (for select purposes) joins on the reference in the composite id. An example of this would be where you want to fetch all the records and then do some projections of values from the parent record. I will log an issue for this specific broken usage.

Sweet! Here's another work-around to tide people over until the next version of NHibernate is released: because has been fixed since v2.1.1, you can avoid this bug by extracting your composite key out to it's own class as described here: http://nhforge.org/doc/nh/en/index.html#components-compositeid. Please note that you will also have to change any code that refers to the composite-id properties. For example, if you previously referred to the property like "child.Parent", now you will have to do "child.Id.Parent".

Pull request by Daniel A. Schilling merged to master

... and is another duplicate. is related but distinct. This issue (NH-2033), NH-2469, and apply to embedded composite id's (composite-id's with no "name" attribute), while applies to named composite-id's.