1.0.2

Hierarchy: Parent-Child-Grandchild, both 1:M

Query: "from Child ch where :parm in elements(ch.Grandchild)"

Parameter passed: session.SetEntity("parm", someParentObject)
(YES - incorrect object submitted, the intent was to test type validation)

Result - no Exception raised, SQL successfully generated, Parent's ID substituted as the param value, SQL executed, some list of Child objects returned.

Problem: the actual param type was obviosly incorrect; but accepted by the system

Question: the lack of Param type validation - is this by design, or has some other explanation?

thank you

HQL parser in NHibernate is not sophisticated enough to do type checking, and besides it would slow things down.

This creates an opening for some fairly pernicious bugs particuarly for large projects with multiple programmers since the incorrectness of the query will be very hard to detect.

Are there common patterns people use to validate Query parameters for type correctness.

Your point about expense of type checking is well taken. It would be nice if you could flag the parser to optionally perform the check but it would probably be a beast to code.

To all the authors and contribs. nHib is an impressive piece of work thanks for creating it.

Cheers,

Terence