[jira] [Commented] (OLINGO-414) Cannot Filter on Navigation Property

2016-07-04 Thread Alex Key (JIRA)

[ 
https://issues.apache.org/jira/browse/OLINGO-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361379#comment-15361379
 ] 

Alex Key commented on OLINGO-414:
-

Hi,

perhaps to keep it simple (or at least on the same level of complexity as 
current solution has) we can use
{code}
...
FROM SalesOrderHeader e1
JOIN SalesOrderItem e2
WHERE e2.delivered = true
...
{code}
for all types of relationships (*ToOne and *ToMany)?

I.e. if filter contains navigation, then (a) use join context and (b) for each 
such filter item generate JOIN.

Best regards,
Alex

> Cannot Filter on Navigation Property
> 
>
> Key: OLINGO-414
> URL: https://issues.apache.org/jira/browse/OLINGO-414
> Project: Olingo
>  Issue Type: Bug
>  Components: odata2-jpa
>Affects Versions: V2 2.0.0
>Reporter: Simon Carroll
>Assignee: Michael Bolz
> Attachments: olingo-414-exception.diff, olingo-414-patch.diff
>
>
> We are receiving an error when we try to filter on a navigation property.  In 
> our solution we have a Notification entity and a User entity, we would like 
> to retrieve a specific Notification but only if it is linked to the 
> requesting user.  This would involve an ODATA request which filters on both 
> the UserId and the NotificationId.  An example of the URL we are invoking is:
> dspplatform.svc/Notifications?$filter=NotificationId%20eq%204%20and%20UserDetails/UserId%20eq%202
> This returns the following error:
> org.apache.olingo.odata2.core.edm.provider.EdmNavigationPropertyImplProv 
> cannot be cast to org.apache.olingo.odata2.api.edm.EdmProperty
> Can you please advise on how to perform filters on a Navigation property as 
> we need this as part of our core functionality?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (OLINGO-414) Cannot Filter on Navigation Property

2016-07-04 Thread Alex Key (JIRA)

[ 
https://issues.apache.org/jira/browse/OLINGO-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361379#comment-15361379
 ] 

Alex Key edited comment on OLINGO-414 at 7/4/16 2:21 PM:
-

Hi,

perhaps to keep it simple (or at least on the same level of complexity as 
current solution has) we can use
{code}
...
FROM SalesOrderHeader e1
JOIN e1.salesOrderItem e2
WHERE e2.delivered = true
...
{code}
for all types of relationships (*ToOne and *ToMany)?

I.e. if filter contains navigation, then (a) use join context and (b) for each 
such filter item generate JOIN.

Best regards,
Alex


was (Author: alexkey):
Hi,

perhaps to keep it simple (or at least on the same level of complexity as 
current solution has) we can use
{code}
...
FROM SalesOrderHeader e1
JOIN SalesOrderItem e2
WHERE e2.delivered = true
...
{code}
for all types of relationships (*ToOne and *ToMany)?

I.e. if filter contains navigation, then (a) use join context and (b) for each 
such filter item generate JOIN.

Best regards,
Alex

> Cannot Filter on Navigation Property
> 
>
> Key: OLINGO-414
> URL: https://issues.apache.org/jira/browse/OLINGO-414
> Project: Olingo
>  Issue Type: Bug
>  Components: odata2-jpa
>Affects Versions: V2 2.0.0
>Reporter: Simon Carroll
>Assignee: Michael Bolz
> Attachments: olingo-414-exception.diff, olingo-414-patch.diff
>
>
> We are receiving an error when we try to filter on a navigation property.  In 
> our solution we have a Notification entity and a User entity, we would like 
> to retrieve a specific Notification but only if it is linked to the 
> requesting user.  This would involve an ODATA request which filters on both 
> the UserId and the NotificationId.  An example of the URL we are invoking is:
> dspplatform.svc/Notifications?$filter=NotificationId%20eq%204%20and%20UserDetails/UserId%20eq%202
> This returns the following error:
> org.apache.olingo.odata2.core.edm.provider.EdmNavigationPropertyImplProv 
> cannot be cast to org.apache.olingo.odata2.api.edm.EdmProperty
> Can you please advise on how to perform filters on a Navigation property as 
> we need this as part of our core functionality?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)