Composite id's on columns with null value doesn't work anymore

Description

In version 2.1 a mapping like this worked perfectly even with null values in the key columns:

With the new 3.2 it doesn't work anymore. If one of the key columns contains null values Nhibernate will return a list with the correct number of items but with every item null.

Is this by design?

Environment

None

Activity

Show:

Alex Zaytsev 
July 22, 2018 at 11:54 AM

Moved here.

Dmitry Gusarov 
April 17, 2017 at 6:18 PM
(edited)

Just spent 2 hours on 2 person to realize that there is actually known bug. Very unexpected behavior and there are no exceptions thrown about this...
our version 3.3.3 sp1

Oskar Berggren 
October 27, 2013 at 8:23 AM

Funny issue when deleting collection elements where I suspect that the parent is using a composite key: http://stackoverflow.com/questions/19612354/nhibernate-delete-sql-null-check-issue

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Who's Looking?

Open Who's Looking?
Created January 12, 2012 at 1:33 PM
Updated July 22, 2018 at 11:54 AM
Who's Looking?