[
https://issues.apache.org/jira/browse/OLINGO-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15591920#comment-15591920
]
Alexandre Desjardins commented on OLINGO-1010:
----------------------------------------------
Thank you for the followup [~grande].
I had another quick question regarding the queries generated. It seems that
when we are using expand with other entities, the expanded entities are not
limited by the root entity. For example, if I make this request:
Tutorial.svc/Companies?$top=3&$expand=Roles
There will be a query to get the root Entity (BusinessPartner) with a limit of
3 applied on it. However, the subsequent query to get the Roles, is getting
every single BusinessPartnerRole (associated with a Company) from the table.
Wouldn't it be better to limit the query to BusinessPartnerRole to only those
associated with BusinessPartners retrieved in the first query? This might be
troublesome if the expanded table is really big as we could potentially fetch
the whole table when only a few tuples are required.
Is there any specific reasoning behind this behavior?
> OData V4 JPA Processor
> ----------------------
>
> Key: OLINGO-1010
> URL: https://issues.apache.org/jira/browse/OLINGO-1010
> Project: Olingo
> Issue Type: New Feature
> Components: odata4-server
> Affects Versions: (Java) V4 4.0.0, (Java) V4 4.2.0, (Java) V4 4.3.0
> Reporter: Oliver Grande
> Attachments: OlingoV4JPA-apache.zip,
> odata-jpa-annotation-0.0.1-SNAPSHOT.jar,
> odata-jpa-metadata-0.0.1-SNAPSHOT.jar, odata-jpa-processor-0.0.1-SNAPSHOT.jar
>
>
> Hello,
> I have created a first version of a JPA Processor for Olingo V4. The
> Processor is, as of now able to generate metadata document and perform GET
> requests. I like to contribute with this to Olingo.
> Regards,
> Oliver
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
