Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What's the currently recommended way of performing partial updates with Web API?

Tags:

I'm wondering how to implement partial updates with ASP.NET Web API's RESTful interface? Let's say for example we are passing objects over the wire of the following structure:

public class Person {     public int Id { get; set; }     public string Username { get; set; }     public string Email { get; set; } } 

How would one support updating just parts of a Person at a time, for example the Email property? Is it recommended to implement this via OData and the PATCH verb, or would it be better to implement PATCH oneself?

like image 876
aknuds1 Avatar asked Jan 05 '13 23:01

aknuds1


People also ask

Which of the following method is used to update an object partially using Web API?

PUT. The HTTP PATCH method should be used whenever you would like to change or update just a small part of the state of the resource.

Which HTTP method will perform partial update to a resource?

The HTTP PATCH request method applies partial modifications to a resource. PATCH is somewhat analogous to the "update" concept found in CRUD (in general, HTTP is different than CRUD, and the two should not be confused). A PATCH request is considered a set of instructions on how to modify a resource.

Which API method is used to update records?

You use the sObject Rows resource to update records. Provide the updated record information in your request data and use the PATCH method of the resource with a specific record ID to update that record. Records in a single file must be of the same object type.

How do I update data in Web API?

Update operations use the HTTP PATCH verb. Pass a JSON object containing the properties you want to update to the URI that represents the record. A response with a status of 204 No Content will be returned if the update is successful.


1 Answers

There is no support in the current latest stable release of Web API (from August 2012). So if all you want to use is Web API RTM, you would have to implement the whole plumbing yourself.

With that said, OData prerelease package supports partial updates very nicely through the new Delta<T> object. Currently the Microsoft.AspNet.WebApi.OData package is at RC version already (0.3) and can be obtained from here: http://www.nuget.org/packages/Microsoft.AspNet.WebApi.OData

Once you install that, you can then use that accordingly:

[AcceptVerbs("PATCH")] public void Patch(int id, Delta<Person> person) {     var personFromDb = _personRepository.Get(id);     person.Patch(personFromDb);     _personRepository.Save(); } 

And you'd call it from the client like this:

$.ajax({     url: 'api/person/1',     type: 'PATCH',     data: JSON.stringify(obj),     dataType: 'json',     contentType: 'application/json',     success: function(callback) {                    //handle errors, do stuff yada yada yada     } }); 

The obvious advantage of this is that it works for any property, and you don't have to care whether you update Email or Username or whatnot.

You might also want to look into this post, as it shows a very similar technique http://techbrij.com/http-patch-request-asp-net-webapi

EDIT (more info): In order to just use PATCH, you do not need to enable anything OData related, except for adding the OData package - to get access to the Delta<TEntityType> object.

You can then do this:

public class ValuesController : ApiController {     private static List<Item> items = new List<Item> {new Item {Id = 1, Age = 1, Name = "Abc"}, new Item {Id = 2, Age = 10, Name = "Def"}, new Item {Id = 3, Age = 100, Name = "Ghj"}};      public Item Get(int id)     {         return items.Find(i => i.Id == id);     }      [AcceptVerbs("PATCH")]     public void Patch(int id, Delta<Item> item)     {         var itemDb = items.Find(i => i.Id == id);         item.Patch(itemDb);     } } 

If your item is, let's say:

{     "Id": 3,     "Name": "hello",     "Age": 100 } 

You can PATCH to /api/values/3 with:

{     "Name": "changed!" } 

and that will correctly update your object.

Delta<TEntity> will keep track of the changes for you. It is a dynamic class that acts as a lightweight proxy for your Type and will understand the differences between the original object (i.e. from the DB) and the one passed by the client.

This WILL NOT affect the rest of your API in any way (except of course replacing the DLLs with newer ones to facilitate the OData package dependencies).

I have added a sample project to demonstrate the work of PATCH + Delta - you can grab it here (it.s VS2012) https://www.dropbox.com/s/hq7wt3a2w84egbh/MvcApplication3.zip

like image 122
Filip W Avatar answered Nov 15 '22 15:11

Filip W