This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
With version 2.2.1095.11159 I had no problem with fetch a Discriminator with/without queryexpression against the ThroughAssociation relations. With version 2.2.1215.11784 it tries to fetch Discriminator column from the relation tables. I haven't compare the source code, blog or forum that this "feature" is correct or its a bug... |
|
|
I think the only change we've made in that area was to fix a bug where discriminators were not being applied when eager-loading an association to a derived class. What's the problem you're seeing? Is the SELECT failing due to an invalid column? Could you post details of how to reproduce the problem and what is the error you're seeing? Thanks! |
|
|
It looks like it trying to resolve the MyObjectTypeId from MyThroughAssociationObject
Mindscape.LightSpeed.LightSpeedException: Query Error: Could not find field [MyObjectTypeId] on model [MyThroughAssociationObject] |
|
|
Mindscape.LightSpeed.LightSpeedException: Query Error: Could not find field [MyObjectTypeId] on model [MyThroughAssociationObject]
It should got the MyObjectTypeId from the MyObject, not MyThroughAssociationObject |
|
|
Mindscape.LightSpeed.LightSpeedException: Query Error: Could not
find field [MyObjectTypeId] on model [MyThroughAssociationObject]
It should got the MyObjectTypeId from the MyObject, not MyThroughAssociationObject |
|
|
When posting this, i'm getting a error from the forum |
|
|
Thanks for the repro. This is not an issue with through associations but with query expressions involving traversals -- in your example, Entity.Attribute("ActorGroups.ActorGroupId") -- on a discriminated type. The 20 August nightly will contain a candidate fix. I've tested it against your repro project; please let us know if you still see problems in more complex scenarios. |
|
|
thanks
|
|