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 do this according to the LS documentation:
Exception: The given Key was not found in the dictionary Reason (I think): the subquery alias used is q1 the alias for the first entity is t0 when creating the command ls is trying t1 for the second table and fails when i use
I do get duplicate key error. So I think LS fails to translate the aliases correctly. Is that a bug? I guess it is then I changed it to the actual join I wanted to do with my generic routine like this
and this actually works as long as I force the mapping .. when I do not add the mapping I get the key not found in dictionary exception. Ok, it works for me now but it should work without the custom mapping though. regards gmd |
|
|
Ive tried checking this here but this type of query (original syntax in your post) works fine for me, there is no confusion around the aliasing being used. Is it possible for you to post a repro project (unit test or console app) which causes the issue you are seeing and I can have a look into this as it sounds like a bug.
|
|
|
ok thanks for trying .. I have not tested it in an isolated environment .. simply no time .. and also have not even a minute to isolate the problem in a small app .. maybe some time later I will leave at that right now, because my approach in using the joins and subqueries might change anyway with the new insight of eager loading and using object graphs rather than sql joins. Thanks Jeremy regards gmd |
|