[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6749?page=c...
]
John Verhaeg resolved HHH-6749.
-------------------------------
Resolution: Fixed
Turns out I misinterpreted the problem, and the initial "fix" was incorrect.
Turns out this is a problem with the SQLServer2005Dialect and all of its subclasses.
Modified SQLServer2005Dialect.getLimitString() to add limit criteria that uses the max row
value in an exclusive manner
FooBarTest.testLimit() fails on MS SQL Server due to dialect
interpretation of max row
--------------------------------------------------------------------------------------
Key: HHH-6749
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6749
Project: Hibernate Core
Issue Type: Bug
Components: testsuite
Affects Versions: 4.0.0.CR4
Environment: MS SQL Server
Reporter: John Verhaeg
Assignee: John Verhaeg
Fix For: 4.0.0.next
The underlying method to get the max row already documents the possible differences in
interpretation by dialects and a method (useMaxForLimit) already exists on the dialect
class to determine which interpretation to use; the test just needs to make use of this
dialect method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira