[
https://issues.apache.org/jira/browse/OLINGO-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Amend resolved OLINGO-927.
------------------------------------
Resolution: Information Provided
Assignee: Christian Amend
For the OData V2 protocol we have a JPA framework which takes care of this. The
ultimate goal in V4 would be to have the same.
Even now you could implement the Processor on your own to generate the SQL
which is used to fetch the data.
If you would like to contribute here is a guide:
http://olingo.apache.org/contribute.html
> URL to SQL Conversion for filtering data
> ----------------------------------------
>
> Key: OLINGO-927
> URL: https://issues.apache.org/jira/browse/OLINGO-927
> Project: Olingo
> Issue Type: Question
> Components: MISC
> Reporter: VIJAYASIMHA R NAGA
> Assignee: Christian Amend
> Priority: Minor
>
> Most of the OData examples are built around post fetch filtering which could
> probably be a performance concern for OData Services built over Database
> driven projects where there is an opportunity to transpose the filtering
> attributes provided in the URL to a where clause of an SQL instead of parsing
> bulk of data retrieved from DB to apply the filters, is any
> framework/solution planned around this topic ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
