WCF Data Services Expand behaves unexpectedly when certain entity page sizes are set?
There is a bug that I found relating to using Expand with server-driven paging in . NET Framework 4, but I thought that it only affected entities with compound keys and when using the OrderBy option, neither of which seem to apply here. Still it definitely sounds like a bug Have you tried using Atom instead of JSON, and if so are the entities in the expand still missing?
There is a bug that I found relating to using Expand with server-driven paging in . NET Framework 4, but I thought that it only affected entities with compound keys and when using the OrderBy option, neither of which seem to apply here. Still it definitely sounds like a bug.
Have you tried using Atom instead of JSON, and if so are the entities in the expand still missing?
. NET 4, from the last Service Pack. We actually use Atom normally for this, I just used JSON to post the example because it's more terse.
– Jeffy May 10 at 6:59.
Your query: localhost:62946/TestWCFDataService. Svc/Towns('Berlin')? $expand=Ladies/Gentleman doesn't expand Ladies, only the Gentelman.
The query should look like: localhost:62946/TestWCFDataService. Svc/Towns('Berlin')? $expand=Ladies,Ladies/Gentleman.
Hope this helps! Monica Frintu.
Expanding Ladies/Gentlemen also expands Ladies. This behaviour is documented (albeit vaguely) in the OData spec (see the second $expand example), and when one modifies the query as you have described the results are the same. – Jeffy May 10 at 23:20.
The expand only includes one of the Lady objects (although at least her Gentleman is included). It doesn't matter how large the page size is set to, the query still only returns one object in the expanded collection. It also does not matter whether or not the page size is set on one or both of the expanded entities, as long as one of them has a page size set then only one of the Lady objects will be eagerly loaded.
"A URI with a $expand System Query Option indicates that Entries associated with the Entry or Collection of Entries identified by the Resource Path section of the URI must be represented inline (i.e. Am I misreading the spec? Should I have expected this behaviour?
I just want to be able to limit the page size of the entity sets when accessed directly but also have them eagerly loadable. Is it a bug in WCF Data Services? (or my code?
But I can't find an explanation of why the page size for the related entity sets seems to default to 1 no matter what page size is specified. Yet more info: the version in question is on . NET 4 version 4.0.30319 with System.Data.
Services version 4.0.0.0. It's the version that comes in the box with Visual Studio 2010 (with SP1 installed). A sample solution showing the behaviour is now up in a github repository.
It's got paging turned on in the InitializeService method and a DB creation script that also adds some sample data so that we're on the same page.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.
Related Questions
Win32: CredUIConfirmCredentials behaves unexpectedly?
Insert New Data using Linq — WCF Data Services (formerly ADO.NET Data Services)?
WPF App with WCF Data - EF, Linq2Sql or WCF Data Services - None Seem 'Easy?
Jquery expand/collapse--expand programmatically from colorbox page reload?
When should I choose to use WCF versus WCF Data Services?
How to prepare data for display on a silverlight chart using WCF RIA Services + Entity Framework?