Not both...HQL don't change the meaning of your query. IMO, Criteria should throw an exception and not add 'WHERE 1=2'.
2009/4/10 kor <[email protected]> > > hi, i see that > > if i use an iquery with ".... where item.Id in (:myList) ......" > and .SetParameterList("myList", anEmptyList) > > there's a NullReferenceException (this is where it is thrown) > (NHibernate-2.0.1.GA-src\src\NHibernate\Engine\TypedValue.cs(25,0) ) > > if i use ICriteria with Expression.In("Id", myList) all work fine and > the generate SQL is something as > WHERE 1=2 > > > i see that there were in the past a lot of discussions about how > manage the logic of "contained in an empty list" so i don't think that > this is a bug so my question is > > why there have 2 different behaviour? i think that using iquery or > icriteria is only a question of taste when doing a job that both can > do. > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
