Sql Generator

["anu238 ." <an...@gmail.com>]

All,
I was going through the tutorials for odata4 I found that Apache olingo
does not have a SQL generator as a result if say I want to return a product
with id=1 then we need to first get all the products and then filter it by
id=1. For a toy example this is okay but in practice you would want to get
only the relevant entries in this case products with id=1 so that
application does not need to do filtering . How are you guys handling this?
Thanks
Anurag

Re: Sql Generator

["anu238 ." <an...@gmail.com>]

Hi Michael,
Thanks for your kind response. You are right it is not part of the spec,
but I see that olingo odata2.0 for java does supports JPA extension, hence
I was wondering if there is some way out to handle what I described above
in Olingo 4.0, looks there isn't.
Thanks,
Anurag
P.S If anyone knows of any JPA extension which can be used with Olingo 4.0
please let me know thanks a lot

On Fri, Jan 29, 2016 at 12:17 PM, mibo <mi...@apache.org> wrote:

> Hi Anurag,
>
> Apache Olingo is a Java library that implements the Open Data Protocol
> (OData).
> Hence such features like a SQL generator or a JPA extension are not in the
> main scope of Olingo.
>
> Based on that such optimization as you describe has to be handled by the
> service developer and not by the core OData library (i.e. Olingo).
>
> Best Regards,
> Michael
>
>
>
>
> On Jan 28, 2016, at 3:51 AM, anu238 . <an...@gmail.com> wrote:
>
> All,
> I was going through the tutorials for odata4 I found that Apache olingo
> does not have a SQL generator as a result if say I want to return a product
> with id=1 then we need to first get all the products and then filter it by
> id=1. For a toy example this is okay but in practice you would want to get
> only the relevant entries in this case products with id=1 so that
> application does not need to do filtering . How are you guys handling this?
> Thanks
> Anurag
>
>

Re: Sql Generator

[mibo <mi...@apache.org>]

Hi Anurag,


Apache Olingo is a Java library that implements the Open Data Protocol (OData).
Hence such features like a SQL generator or a JPA extension are not in the main scope of Olingo.


Based on that such optimization as you describe has to be handled by the service developer and not by the core OData library (i.e. Olingo).


Best Regards,
Michael










> On Jan 28, 2016, at 3:51 AM, anu238 . <an...@gmail.com> wrote:
> 
> 
> All,I was going through the tutorials for odata4 I found that Apache olingo does not have a SQL generator as a result if say I want to return a product with id=1 then we need to first get all the products and then filter it by id=1. For a toy example this is okay but in practice you would want to get only the relevant entries in this case products with id=1 so that application does not need to do filtering . How are you guys handling this?
> Thanks
> Anurag