[
https://issues.apache.org/jira/browse/OLINGO-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185110#comment-14185110
]
Michael Bolz commented on OLINGO-461:
-------------------------------------
Hi [~sandijs],
by default the Olingo OData library does not cache any content.
Either it is cached by browse, some proxy or the implemented OData Service
itself.
Beside of that the GET request looks good and as you mention you get the
correct entity back.
Do you implement the OData service by yourself?
Kind regards,
Michael
> Requesting data with filter returns correct data records, BUT the contents of
> them is old cached version before the data changes which were used to filter
> updated data records
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OLINGO-461
> URL: https://issues.apache.org/jira/browse/OLINGO-461
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core, odata2-jpa
> Affects Versions: V2 2.0.0
> Environment: Tomcat 7, MySQL
> Reporter: Sandijs Aploks
> Assignee: Michael Bolz
> Priority: Critical
>
> I updated one data record with new values so that it could be queried by this
> request correctly:
> "GET
> /interactive-riga-odata/webservices.svc/Statuss?$filter=(Updated%20gt%20datetime%272014-10-15T12:25:44.054%27)
> HTTP/1.1" 200 1169
> The request returns correct data record, BUT the contents of the data record
> is old cached version.
> Is this supposed to be this way? If so, how to switch off the caching?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
