Fabio, could you review my proposed patch for NH-2214 for inclusion in 3.2? It passes all tests (of course). Please let me know if you have any questions about it. I think it is actually fairly low risk, as it caters for a particular case where DISTINCT is used in a paged query. This is done with an alternate query, and non-distinct queries are still done as before.
The changes toDialectTest.MsSql2005DialectFixture.GetLimitString were required because the SQL output by the dialect is different. Also, the SQL generated by the previous code was in fact incorrect, and exhibited the exact problem described in NH-2214 - applying distinct on a row containing the ROW_NUMBER() OVER (ORDER BY ...) Thanks Julian Thanks. On 20 June 2011 20:12, Fabio Maulo <[email protected]> wrote: > Hi. > NH3.2.0Beta2 was released. > The next will be a ReleaseCandidate so, please, stop breaking change and > stuff like that. > Thanks. > > -- > Fabio Maulo > >
