Hi, Referring to an (The exception is an Sorry if that wasn't clear - I can post sample code if it will help. Cheers, Matt. Edit: Gah, I'm not supposed to post my response as an answer, but a comment won't accommodate my response, so I'll just have to edit it and jam it here. Not my favourite support tool =/ Hi Alex, Thanks for the quick response (and for tidying up my post). Yes, I'm using PairTo with the EntitySet. So, my case is something like this:
If I do something like this (assume all the appropriate constructors are in place):
then everything writes through to the database correctly. If I then retrieve the records like this:
then the list is loaded correctly, and I can iterate through the correctly loaded types and their respective properties (i.e. there is no "slicing"). However, if I simply load the item and attempt to access it like this:
then I get the error I originally posted. From your previous post it sounds like this is expected behaviour. If so, why is loading automatically through use of an EntitySet different from issuing a LINQ query using the base type? Cheers, Matt. |
Do you use If there is something else, probably, this is a bug. |
New info added in edit, as comment won't accommodate it.
Most likely, there is a bug. It could be already fixed in today's nightly build - we've fixed one pairing-related issue there.
Could you publish the stack trace? We'll add the test for this case anyway, but stack trace should help us to identify the issue faster.
I'd be happy to publish the stack trace, but the last build seems to have corrected the fault, so I guess you don't need it ;)
Thanks for fixing this so quickly.
Good then ;)