Since no one answered this question in 3 days, can I assume NH doesn't support this? Is there any way to put this in the product backlog?
Thanks, Dor. On May 24, 4:17 pm, Dor Rotman <[email protected]> wrote: > Hello, > Lets assume I have this piece of code: > > UnitOfWork.Current.Session.CreateCriteria<T>() > .Add(Restrictions.In(propertyName, (ICollection)collection)) > .Future<T>(); > > I run this code TWICE, on different objects. However, both queries > check for membership against the same collection. > > The result is that for each query of the two, the collection turns > into parameters, like this: > SELECT FROM ... WHERE FIELD_NAME IN (@p1, @p2, ... @pN) > SELECT FROM ... WHERE FIELD_NAME IN (@pN+1, @pN+2, ... @p2N) > > Since the collections are the same, is there anyway for NH to send the > parameters list @p1 .. @pN and use it twice in the SQL? > I'm reaching the 2100 parameters limit in MS SQL..:) > > Thanks, > Dor Rotman. > > -- > 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 > athttp://groups.google.com/group/nhusers?hl=en. -- 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.
