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
|
I have some entities with parent-child relationships. Job -> Runs -> Tools. A dynamic query engine builds up the where clause to search Jobs. I don't have the option to rearrange the query at this time. The following query works just fine (where I am searching for a Job that has a tool with Seal Length >= 2): from job in UnitOfWork.Query The following query (Seal Length between 2 and 10) fails (as does any query with ANDed/ORed conditions two levels deep). from job in UnitOfWork.Query Here is the error message: Cannot use Tools[SealLength = True] as part of a logical expression in an Any or All expression. I can successfully combine two conditions within Runs.Any(), but not in the second Any() down. If there's any way a fix for this could make it into the nightly, our client would be very happy. In the meantime, they are unable to run any Between queries on tools in their database. |
|
|
Ive had a look into this one - unfortunately its not going to be a quick fix to resolve this as it will require some internal rejig of how we handle Any/All. Ill continue working on this and update you once we have made progress on this.
|
|
|
Any update on this one? We're getting pretty close to the live deployment of our solution and hoping that our search infrastructure will be working by then. Date Range searches on the children of the records we selected are a critical feature and still throwing exceptions. :( |
|
|
I have added a candidate fix for this which will be available in the next nightly build for you. Let me know if this covers the issue you are seeing once you have had a chance to download the nightly.
|
|
|
I thought I had verified the fix, but I had tested with a field that actually didn't fit the criteria for the bug. With the following structure, I now get a different error. Parent -> Collection Query Parent.Children.Any(Child.Grandchildren.Any( Grandchild.Field (int) between 1 and 100) :
|
|
|
Ive tried reproducing this here with an example model but the queries are working for me - are you able to post a minimal repro project which we can use to have a look into this for you please.
|
|
|
Here you go. |
|
|
Just an update to let you know we are still working on getting in a fix for this and I will post an update once we have made some progress on this.
|
|
|
I have added a candidate fix for the latest issue which will be available in the next nightly build for you. Let me know if there are any other outstanding issues you notice after installing the updated build.
|
|