[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5715) Using row_number with the SQLServerDialect makes select distinct useless

[Yoryos Valotassios (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42568#action_42568 ] 

Yoryos Valotassios commented on HHH-5715:
-----------------------------------------

@Maros: you are right. I'm just checking for a distinct keyword with in the select statement. I think there is the easy workaround to search for the "select distinct" phrase with in the sql query in order to fire the replacement. @Strong: Pull request is on the way, but should I open a new issue first? 

> Using row_number with the SQLServerDialect makes select distinct useless
> ------------------------------------------------------------------------
>
>                 Key: HHH-5715
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5715
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>            Reporter: Yoryos Valotassios
>            Assignee: Strong Liu
>             Fix For: 3.6.1, 3.x
>
>
> Given class A with one to many relations to class B, when trying to get paginated data with SQLServerDialect from class A with a join clause to class B will dublicated A instances. That is because the row_number function will introduce another value to the select statement which will alway be different for each row. I found a work around using group by. Did not have time finish the test cases yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira