Supporting OData CRUD Operationshttp://www.asp.netTue, 21 May 2013 04:30:18 GMTumbracoComments for Supporting OData CRUD OperationsenComment Posted by breyedhttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsFri, 08 Mar 2013 10:57:18 GMT00000000-0000-0000-0000000018622The samples that modify the database all appear to contain race conditions. The boilerplate code generated by Visual Studio for a new Web API with EF controller contains catches blocks for DbUpdateConcurrencyException. Is there some similar technique to address changes that may occur, say, between _context.Products.Any and SaveChanges? Additionally, calling Any followed by SaveChanges involves two database round trips. Is there a best practice to make only one?

]]>Comment Posted by breyedhttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsFri, 08 Mar 2013 11:03:31 GMT00000000-0000-0000-0000000018623The banner on top saying "This topic describes pre-release features" is out of date. OData over ASP.NET Web API is now a stable release.

]]>Comment Posted by breyedhttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsFri, 08 Mar 2013 17:49:34 GMT00000000-0000-0000-0000000018635This StackOverflow question demonstrates a way to doing updates that avoids the race condition and the extra database round trip:

stackoverflow.com/

]]>Comment Posted by MikeWassonhttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsMon, 11 Mar 2013 18:53:42 GMT00000000-0000-0000-0000000018657@breyed: Thanks for the comments. I'll remove the pre-release note and update the example code to use RaghuRam's approach.

]]>Comment Posted by stevo.zilikhttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsTue, 12 Mar 2013 21:15:09 GMT00000000-0000-0000-0000000018676Hi Mike, great work. Question regarding CRUD (create for now). The Request Form Body as Json:

{"Id":"","ModFamilyId":"80daa9a1-f482-4ad7-b6e3-7a9ae3483a0e","FromSessionId":8,"FromSessionName":"""__metadata":{"type":"LiveRacers.Web.ApiModels.ModMappingModel"}}

In EntitySetController Post, the 'entity' is null. The Model defines all those properties (except the __metadata). Same solution works with pure Web Api. Any idea why the request form body json data is not serialized into a new model?

]]>Comment Posted by aconsolatihttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsWed, 13 Mar 2013 02:50:44 GMT00000000-0000-0000-0000000018678@stevo.zilik I also have the entity parameter being passed as null into both the CreateEntity and UpdateEntity methods of my EntitySetController-derived class. I'm sending the payload from Fiddler.

The post body I'm sending is plain JSON with the correct entity properties and no metadata:

{"Entry_Code":543,"Clipboard_Code":388,"Clinic_Code":1,"Client_Number":"ABC123","Patient_Number":"XYZ","Consultation_Number":null}

The content type for the header is set to:

Content-Type: application/json;

]]>Comment Posted by aconsolatihttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsThu, 14 Mar 2013 19:17:20 GMT00000000-0000-0000-0000000018703@stevo.zilik OK, I have resolved this issue with entity being passed as null.

First install latest nightly for OData via PM console:

Install-Package Microsoft.AspNet.WebApi.OData -Source www.myget.org/ -Pre

This updated 4 assemblies, including Microsoft.AspNet.WebApi.OData 4.0.0 to 5.0.0-alpha-130314.

Note I also had to specify charset in PUT request as:

Content-Type: application/json; charset=utf-8

Hope that helps you

]]>Comment Posted by stevo.zilikhttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsFri, 15 Mar 2013 14:31:23 GMT00000000-0000-0000-0000000018710@aconsolati - thanks mate, but its still not working... can you try a POST request?

I've updated the package to 5.0.0-alpha-130315 and set the Content-Type application/json; charset=utf-8, still null

]]>Comment Posted by stevo.zilikhttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsSat, 16 Mar 2013 09:02:29 GMT00000000-0000-0000-0000000018715Hi Mike, would it be possible to post some working examples of using odata CRUD with json javascript client. Currently I'm struggling to get anything working with the odata routing...

]]>Comment Posted by dmaxwellhttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsTue, 02 Apr 2013 21:48:05 GMT00000000-0000-0000-0000000018832It would be nice to see examples using Fiddler2 or JavaScript working together with these OData services.

]]>Comment Posted by BrunoMonhttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsThu, 11 Apr 2013 11:01:58 GMT00000000-0000-0000-0000000018893Hi Mike, great post!

I need to obtain an updated entity in the browser, but the Odata response status code for put operations is 204 (No Content).

Is there any way to send the updated entity back to the client ?

thanks

]]>Comment Posted by DamianReeveshttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsThu, 16 May 2013 10:27:51 GMT00000000-0000-0000-0000000019117Mike is there a way to generate service references that reuse a shared type like in other WCF based services. For my .NET Client it would be nice if I could use a type from a shared assembly.

]]>Comment Posted by Appiezhttp://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-crud-operationsTue, 21 May 2013 04:30:18 GMT00000000-0000-0000-0000000019149Mike, thanks for the tutorials. I learned a lot from them.

Past weekend i've created a odata service myself and some things took me a while to figure out, therefor i will share them with other readers. But, because the comments are limited to a certain characters, i've placed it on pastebin:

pastebin.com/

]]>