A client of ours noticed some odd behavior when sorting and paging. Upon further investigation, it appears to be the same issue specified in NH-1637, where the rownum pseudo-column is used to handle paging from SetFirstResult() and SetMaxResults() on the ICriteria.
We're using version 2.1.0.3001 of nHibernate with version 1.0.0.0 of Sharp Architecture. I looked at the patch specified in NH-1638 and it seems to correct the issue, but it doesn't appear that the patch has made it into any version of nHibernate. Can anyone expand upon this, or offer some advice on how to correct the issue with minimal implication to the application? Thanks for your time, Sam Ferrise [email protected] -- 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.
