You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Archana Rai (JIRA)" <ji...@apache.org> on 2018/09/26 10:55:00 UTC

[jira] [Resolved] (OLINGO-1298) Hibernate latest version compliance

     [ https://issues.apache.org/jira/browse/OLINGO-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Archana Rai resolved OLINGO-1298.
---------------------------------
    Resolution: Fixed

This issue has been fixed: [https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=e2b2b191f86fa5ee93a8f452c4392dc14a6648cc]

Thanks,

Archana

>  Hibernate latest version compliance
> ------------------------------------
>
>                 Key: OLINGO-1298
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1298
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-jpa
>    Affects Versions: V2 2.0.11
>            Reporter: Archana Rai
>            Priority: Minor
>             Fix For: V2 2.0.11
>
>
> Newer Hibernate versions, e.g. 5.2.x, has changed the query handling. As a result, when in combination with Olingo there are problems with ordinary EntitySet calls (something like “/foo/Persons” in order to get all Person objects) delivers an empty result, although there is data in the database and single accesses delivered them (“/foo/Person/3453” where “3453” is the person key).
> EntitySet URL works as soon as we add the $top parameter to it (“/foo/Persons?$top=100”).
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)