>>> In fact, you >>> should get the exception already when bigNumber is greater than 0, >>>since the SQL with the count will only generate one row. Now I get exception only if bigNumber large enough that result collection contains 0 items. I think that Count() simply must return 0 in this situation.
>>>On the other hand, this seems like a rather unusual query - why do you need it? For application service with paging ( Skip(pageSize*pageNumber).Take(pageSize) ). If pageSize big and result page contains 0 items call Count() results to crash. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/zz5TymD4SrsJ. 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.
