Not an Issue
Details
Details
Assignee
Unassigned
UnassignedReporter
Taavi Kõosaar
Taavi KõosaarLabels
Components
Affects versions
Priority
Who's Looking?
Open Who's Looking?
Created February 17, 2011 at 7:38 AM
Updated July 13, 2018 at 10:53 AM
Resolved July 13, 2018 at 10:53 AM
A simple NHibernate 3.0 linq (the version released with NH3.0) query:
Works perfectly when the particular unit has reasons, however throws "value cannot be null. Parameter name: item" when no rows are returned. Also the confusing outer exception with message "SQL: SQL not available" is used.
The generated SQL seems correct, but it doesnt seem to handle NULL result.
I saw a BUG NHQ-10, that seemed similar and was fixed, however it doesnt seem so or this is something different. Doesnt seem proper behaviour, should return null or 0 (default(int)).