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
|
We start out by creating a QueryExpression that contains very similar attribute paths (here "string" and "System.Byte[]" are values we're querying for: ( In QueryBuilderBase.VisitTypeModel, queryExpression is {( and on line 473 queryExpression.Rebase is called with an empty context path, and assigned to contextExpression: {A.B[ The problem is that P and Q have been removed and replaced with a combined C[...]. The B entity does not have a C, it should be B.P.C and B.Q.C. Ulitmately this throws an unhandled LightSpeedException, Path component [C] not found in type [B]. I was able to work around this by adding an extra A.B to the beginning of my the attribute paths in the second QueryExpression, ( Apparently this is sufficient to prevent the incorrect simplification, but a correct simplification should be possible. |
|
|
I ran the query with a nightly build, 2.2.20090901. |
|
|
Thanks for reporting this. I've committed a candidate fix and this will be included in nightly builds dated 22 Sept 2009 and above, available from about 1430 GMT. Due to the complexity of your query, I have not tested this with your exact query, but only in a simplified version. (But I did see the same bug and I don't think the additional complexity of your case alters the nature of the bug or fix, so I do believe it should work.) Please let us know if the simplification is still incorrect in your case. |
|
|
The query appears to work as expected with the fix. I haven't verified the simplification, but the evidence suggests it is correct. |
|