[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-317) Allow multiple reads in the same transaction
[ http://tools.oasis-open.org/issues/browse/ODATA-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-317:
-----------------------------
Proposal:
Define request header
Expect: odata.isolation=snapshot
On a batch request this means that all requests in the batch are executed with isolation-level snapshot.
For requests returning a collection (whether within a batch or not) this means that next-links return consistent data with the same snapshot.
Trying to follow a next-link referring to a snapshot that is no longer available MUST return 410 Gone.
was:See summary.
Environment: [Proposed]
Fix Version/s: V4.0_CSD02
(was: V4.0_WD01)
Affects Version/s: V4.0_CSD01
(was: V4.0_WD01)
> Allow multiple reads in the same transaction
> --------------------------------------------
>
> Key: ODATA-317
> URL: http://tools.oasis-open.org/issues/browse/ODATA-317
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData Batch Processing Format
> Affects Versions: V4.0_CSD01
> Environment: [Proposed]
> Reporter: Matthew Borges
> Priority: Minor
> Fix For: V4.0_CSD02
>
>
> Allow change sets of only read operations. The idea being you can get a snap shot of potentially unrelated entities at an instance in time. It would also be useful for deltas where you want to get all the changes (even for unrelated entities) within a single change set request at a certain point of time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]