search

forrestzhu / odata4j

Automatically exported from code.google.com/p/odata4j
0 stars 0 forks source link

Batch support is missing ChangeSets #92

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
The current ODataBatchProvider implements batching by making a series of crud 
calls to the producer, one for each batch item.  The OData protocol says that 
mutators (insert,update,delete) are to be grouped as ChangeSets.  A ChangeSet 
boundary defines a transaction boundary.

In the current implementation the producer has no way of knowing where the 
ChangeSet boundary is and must thus execute each individual batch item in a 
separate transaction.  This negates much of the usefulness of batching 
(atomicity,bulk insert efficiency, etc)

Original issue reported on code.google.com by tony.ro...@gmail.com on 9 Nov 2011 at 11:56

GoogleCodeExporter commented 8 years ago 
This is a very important feature for us.  We are using Odata as our protocol 
for accessing large amounts of technical/engineering data.  There are many 
instances where it is required to batch several updates into a single 
transaction.

Original comment by sketh...@gmail.com on 11 Oct 2012 at 5:50

GoogleCodeExporter commented 8 years ago 
Microsoft LightSwitch is using $batch requests, that do not work with odata4j 
0.7. I did some enhancements to odata4j to support these requests.

Original comment by frank.h....@gmail.com on 19 Mar 2013 at 8:45

GoogleCodeExporter commented 8 years ago 
Is someone working on getting this done or are commits welcome ?

Original comment by jojy...@gmail.com on 30 Aug 2013 at 9:42