Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Sep 05, 2012 08:03 AM by Brauliod
Feb 19, 2012 02:47 AM|LINK
I know that the Beta version provides limited support for OData. Is there a list of the features that are currently supported? Also, are there plans to add more support for OData before the RTM version? I am especially interested in returning a subset
of the properites (i.e. $select=FirstName,LastName) and returning the total number of records that match the filter when using top and skip.
Feb 19, 2012 05:38 PM|LINK
The current support of query string parameters is limited to $top, $skip, $filter and $orderby.
Feb 21, 2012 02:10 PM|LINK
More importantly, we are not currently planning to support $select for this version.
Mar 01, 2012 01:07 PM|LINK
Is there some extensibility point one can hook onto, and maybe add that functionality?
Mar 01, 2012 05:43 PM|LINK
You can always write your own filter to do that processing. Unfortunately, the OData query parser is not public right now. So you cannot build on top of that. Also, could you please let us know what extension/functionality are you looking for ? It would
be a valuable input for the team for later releases :)
Mar 01, 2012 06:47 PM|LINK
Well, it would be cool to be able to have (and advertise) full OData support when you make an API, not just partial support.
Initially, I thought it was a bug, since Scott Gu's
blog post gives the impression that OData querying just works. At least I got that impression.
But thanks for your suggestion, I'll see what I can do with a filter then.
Mar 01, 2012 07:14 PM|LINK
If you are looking for full OData support you should be looking at
WCF Data Services.
Mar 08, 2012 06:02 PM|LINK
I can't speak for everyone else on this thread but what I'M looking for is OData-like querying and hypermedia in Web API. I want to you Web API over OData because I'll have control over what the payload looks like (i.e. not all the extra Atom Pub stuff
that I don't need) but Web API is currently lacking some functionality. I don't need it right this minute but a definitive answer about whether ir not it will be in in the final version of MVC 4 would be appreciated.
Mar 10, 2012 06:56 PM|LINK
Select is essential!
This is designed to work with single page amoung other things.
If I'm listing data I do NOT want to select * unless I'm editing and even then only a single record EVER. Any design that SELECT * on a lot of records (i.e. greater than 1) BAD DESIGN.
In all other cases, select * is just a massive waste of database and bandwidth.
I strongly encourage you to put back Select because without it there is no point to what you're building with MVC.net 4 single pages view because all of the speed improvements using SPA will be flushed down the toilet without select.
Mar 13, 2012 04:11 PM|LINK
MS PLEASE RECONSIDER THIS!
You're making it so that we create apps that SELECT * which is against every rule that you've ever preached and against EVERY RULE THAT ANY SANE PROGRAMMER EVER FOLLOWS.
If you do not fix this, then Web API is completely USELESS for any production application.
We will not use it and we'll advise anyone that listens not to use it because of this massive performance issue.